Triple
T31710460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annie Tee |
E809303
|
entity |
| Predicate | residenceAfterHurricaneKatrina |
P172973
|
FINISHED |
| Object | New Orleans |
—
|
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: New Orleans | Statement: [Annie Tee, residenceAfterHurricaneKatrina, New Orleans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: residenceAfterHurricaneKatrina Context triple: [Annie Tee, residenceAfterHurricaneKatrina, New Orleans]
-
A.
residenceAfterFlood
Indicates that an entity’s place of residence is the one occupied after a flood event has occurred.
-
B.
residenceAfterRescue
Indicates that an entity’s place of residence after being rescued is the specified location.
-
C.
symbolOfPostKatrinaResilience
Indicates that something serves as a representation or emblem of resilience and recovery in the aftermath of Hurricane Katrina.
-
D.
homeStateAfterRelocation
Indicates the state in which an entity is considered to reside or be based after a relocation event has occurred.
-
E.
cityAfterRelocation
Indicates the city where an entity is located after it has been moved or relocated from a previous place.
- 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_69f348df4e048190a4a5a9932ada78d6 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b2d9aad88190a445f8f591cb19fc |
completed | May 3, 2026, 2:28 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b21da77081908c5c015c4606d344 |
completed | May 3, 2026, 2:25 a.m. |
Created at: April 30, 2026, 11:15 p.m.