Triple
T3734852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MS |
E79155
|
entity |
| Predicate | replacedLongForm |
P51351
|
FINISHED |
| Object | Mississippi (full state name in addresses) |
—
|
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: Mississippi (full state name in addresses) | Statement: [MS, replacedLongForm, Mississippi (full state name in addresses)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedLongForm Context triple: [MS, replacedLongForm, Mississippi (full state name in addresses)]
-
A.
replacedStandard
Indicates that one standard has been superseded or taken the place of another standard.
-
B.
replacedWith
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
-
C.
replacedDuring
Indicates that one entity took the place of another entity during a specified time period or interval.
-
D.
replacedBody
Indicates that one entity has taken the place of another entity’s body, substituting it in whole or in part.
-
E.
partlyReplacedBy
Indicates that one entity has been superseded or substituted in part, but not entirely, by 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_69ad8b0e4650819090ad7cef094285e8 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb39dc0881909cd74ff25d8c43a9 |
completed | March 8, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69adc04746588190b0dc535638f23546 |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc45debe48190b1c1f894e02b0316 |
completed | March 8, 2026, 6:47 p.m. |
Created at: March 8, 2026, 3:34 p.m.