Triple
T182260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Orleans |
E3902
|
entity |
| Predicate | dateBecamePartOfUnitedStates |
P6343
|
FINISHED |
| Object | 1803 |
—
|
LITERAL 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: 1803 | Statement: [New Orleans, dateBecamePartOfUnitedStates, 1803]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateBecamePartOfUnitedStates Context triple: [New Orleans, dateBecamePartOfUnitedStates, 1803]
-
A.
dateOfUnionFormation
Indicates the date on which a union was formally established or came into existence.
-
B.
allyOfUnitedStates
Indicates a relationship where an entity maintains a supportive, cooperative, or formally allied partnership with the United States.
-
C.
independenceYear
Indicates the year in which an entity achieved political independence or was formally recognized as independent.
-
D.
independenceDeclaredBy
Indicates that an entity’s independence was formally proclaimed or established by another specified entity.
-
E.
establishedAsNationals
Indicates that certain entities have been formally recognized or constituted as national representatives or national-level organizations.
- 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a2592516748190a85ae58eec191f14 |
completed | Feb. 28, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69a2566ccc288190add5624ede96d82b |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2575e7c7c819095167d8a862c255a |
completed | Feb. 28, 2026, 2:47 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.