Triple
T8873300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michigan |
E211210
|
entity |
| Predicate | hasOrderInUnion |
P159
|
FINISHED |
| Object | 26th state |
—
|
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: 26th state | Statement: [Michigan, hasOrderInUnion, 26th state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrderInUnion Context triple: [Michigan, hasOrderInUnion, 26th state]
-
A.
orderInUnion
chosen
Indicates the relative position or sequence of an entity within a union or ordered collection of entities.
-
B.
hasOrder
Indicates that one entity possesses, is associated with, or is characterized by a specific order, sequence, or arrangement relative to others.
-
C.
hasUnionRepresentation
Indicates that an entity is represented by a labor union in negotiations or employment-related matters.
-
D.
isOrderOf
Indicates that one entity specifies the sequence, arrangement, or ranking in which elements of another entity are organized or occur.
-
E.
includesSuborder
Indicates that one entity contains or encompasses another entity as a subordinate order within its hierarchical structure.
- 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_69ca838e78748190934d82db3104f855 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc612952348190856d6964122c3f01 |
completed | April 1, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2956788190a311c647b4da17a6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:52 p.m.