Triple
T25949444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ancients |
E653927
|
entity |
| Predicate | primaryCityShip |
P193105
|
FINISHED |
| Object | Atlantis |
—
|
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: Atlantis | Statement: [Ancients, primaryCityShip, Atlantis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCityShip Context triple: [Ancients, primaryCityShip, Atlantis]
-
A.
primaryCity
Indicates that one city serves as the main or most important city associated with a given region, entity, or context.
-
B.
principalCityOf
Indicates that a city serves as the main or most important city (often administrative, economic, or cultural center) of a specified region or area.
-
C.
majorReceivingCity
Indicates that one city serves as a primary destination or hub for receiving people, goods, or resources from another location.
-
D.
primaryLocationCity
Indicates the city that serves as the main or primary location associated with the subject.
-
E.
primaryCityAtOtherEnd
Indicates that a given city is the main or principal city located at the opposite end of a specified route, connection, or relationship from another city.
- F. None of above. chosen
Provenance (4 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_69e7ab40ac788190a771bc499eb1ae5f |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
| PDg | Predicate description generation | batch_69fd389b653c81908a97ab2eff98c6ea |
completed | May 8, 2026, 1:12 a.m. |
Created at: April 22, 2026, 8:43 a.m.