Triple
T22830678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Orleans, Louisiana, United States |
E565792
|
entity |
| Predicate | acquiredByUnitedStatesIn |
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, Louisiana, United States, acquiredByUnitedStatesIn, 1803]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquiredByUnitedStatesIn Context triple: [New Orleans, Louisiana, United States, acquiredByUnitedStatesIn, 1803]
-
A.
wasAcquiredByUSAThrough
Indicates that something came under the ownership, control, or sovereignty of the USA by means of a specified acquisition process or event.
-
B.
purchasedByUnitedStatesIn
Indicates that something was bought or acquired by the United States during a specified time period.
-
C.
dateBecamePartOfUnitedStates
chosen
Indicates the date on which an entity formally became part of the United States.
-
D.
acquiredByUSNavy
Indicates that something was obtained or taken into possession by the United States Navy.
-
E.
annexedInYear
Indicates that one entity was formally annexed or incorporated into another in the specified calendar year.
- F. None of above.
Provenance (3 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_69e24585ab1c81909b2b5065d15805d5 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e2ac8d48190b6dc7edc5ad82bc7 |
completed | April 29, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:34 p.m.