Triple
T37056610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Back Up Plan |
E917204
|
entity |
| Predicate | performerFrom |
P199493
|
FINISHED |
| Object | Atlanta, Georgia |
E2602
|
NE FINISHED |
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: Atlanta, Georgia | Statement: [Back Up Plan, performerFrom, Atlanta, Georgia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performerFrom Context triple: [Back Up Plan, performerFrom, Atlanta, Georgia]
-
A.
performerOn
Indicates that an entity serves as the performer or executing agent of an action, event, or work associated with another entity.
-
B.
performerType
Indicates the role or category of performer responsible for carrying out an action or participating in an event.
-
C.
performerFullName
Indicates the complete name of the entity that performs an action or role in the described context.
-
D.
performerCreditedAs
Indicates that a performer is associated with a work under a specific credited name or alias.
-
E.
performedBy
Indicates that an action, task, or event is carried out or executed by a specified agent or entity.
- F. None of above. chosen
Provenance (5 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_69f76e94d0308190a3f06890e133c88e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff3e1762d8819089a60e402e682817 |
completed | May 9, 2026, 2 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a402b9b5bc0819080b43e2c49bb4703 |
completed | June 27, 2026, 7:59 p.m. |
| PD | Predicate disambiguation | batch_69ff3d8c6f308190a0646b1432752eb8 |
completed | May 9, 2026, 1:58 p.m. |
| PDg | Predicate description generation | batch_69ff3e16527c81908c8d89da704ce012 |
completed | May 9, 2026, 2 p.m. |
Created at: May 3, 2026, 4:14 p.m.