Triple
T35010272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boneyard region |
E1009923
|
entity |
| Predicate | centeredOnRuinsOf |
P163458
|
FINISHED |
| Object | Los Angeles |
—
|
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: Los Angeles | Statement: [Boneyard region, centeredOnRuinsOf, Los Angeles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centeredOnRuinsOf Context triple: [Boneyard region, centeredOnRuinsOf, Los Angeles]
-
A.
hasRuinsOn
chosen
Indicates that one location or object contains or is the site of ruins situated upon it.
-
B.
cityRuinsOf
Indicates that a city is located on or associated with the ruins of another, earlier city.
-
C.
ancientCity
Indicates that the subject is a historically old or long-established city, typically originating from ancient times.
-
D.
ancientPolisCenter
Indicates that a location functioned as the central urban, political, or social hub of an ancient polis (city-state).
-
E.
locatedInAncientCity
Indicates that an entity is situated within the boundaries or domain of an ancient city.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7858aa5508190a07dde993b3356fc |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.