Triple
T16394191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlanta Life Insurance Company |
E398136
|
entity |
| Predicate | hasHeadquartersOn |
P123250
|
FINISHED |
| Object | Auburn Avenue |
—
|
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: Auburn Avenue | Statement: [Atlanta Life Insurance Company, hasHeadquartersOn, Auburn Avenue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeadquartersOn Context triple: [Atlanta Life Insurance Company, hasHeadquartersOn, Auburn Avenue]
-
A.
hasManufacturerHeadquartersIn
Indicates that the location specified is the place where the manufacturer’s main headquarters is situated.
-
B.
hasPublisherHeadquartersIn
Indicates that the main corporate headquarters of a publishing entity is located in a specified place.
-
C.
hasOperatorHeadquartersIn
Indicates that the primary operational headquarters of an operator is located in a specified place.
-
D.
hasHeadquartersType
Indicates the specific kind or classification of headquarters associated with an entity.
-
E.
establishesHeadquartersOf
Indicates that an entity selects and sets up the main administrative or operational center (headquarters) for another entity.
- 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e3264538e4819082442d254accf392 |
completed | April 18, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69e226f94dd48190b7b8e0e983738a67 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:08 a.m.