Triple
T24503229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | York, South Carolina |
E617993
|
entity |
| Predicate | namedIndirectlyAfter |
P63
|
FINISHED |
| Object | City of York, England |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: City of York, England | Statement: [York, South Carolina, namedIndirectlyAfter, City of York, England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedIndirectlyAfter Context triple: [York, South Carolina, namedIndirectlyAfter, City of York, England]
-
A.
namedAfter
chosen
Indicates that one entity has been given its name in honor of, or derived from, another entity.
-
B.
namedAfterSince
Indicates that one entity has borne the name of another entity starting from a specific point in time.
-
C.
namedAfterSuccessor
Indicates that an entity is named after another entity that succeeds or follows it in time, position, or sequence.
-
D.
namedAfterPosition
Indicates that an entity is named after a specific position, role, or rank associated with it.
-
E.
usedAfterName
Indicates that one element is used or appears immediately after a name in some context or representation.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e2d7f682108190a1a7ca5fd485ee8a |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:23 a.m.