Triple
T30244407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Bibb |
E769014
|
entity |
| Predicate | hasOrderInOffice |
P351
|
FINISHED |
| Object | 2nd Governor of Alabama |
—
|
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: 2nd Governor of Alabama | Statement: [Thomas Bibb, hasOrderInOffice, 2nd Governor of Alabama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrderInOffice Context triple: [Thomas Bibb, hasOrderInOffice, 2nd Governor of Alabama]
-
A.
orderInOffice
chosen
Indicates that one entity holds a specific sequential position or rank within a defined term or period of holding an office or official role.
-
B.
hasOrder
Indicates that one entity possesses, is associated with, or is characterized by a specific order, sequence, or arrangement relative to others.
-
C.
isOrderedTo
Indicates that one entity has been formally directed or commanded to perform an action or fulfill a duty by another authority.
-
D.
isOrderIn
Indicates that one entity is contained within or belongs to a specified order or sequence of entities.
-
E.
hasWorkOrder
Indicates that an entity is associated with, or linked to, a specific work order that defines tasks or services to be performed.
- 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_69f224831dc08190b2e569b987264057 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: April 29, 2026, 7:39 p.m.