Triple
T21423049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Officer of the Order of Liberty (posthumous) |
E528482
|
entity |
| Predicate | orderRankWithinOrderOfLiberty |
P17947
|
FINISHED |
| Object | Officer |
—
|
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: Officer | Statement: [Officer of the Order of Liberty (posthumous), orderRankWithinOrderOfLiberty, Officer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderRankWithinOrderOfLiberty Context triple: [Officer of the Order of Liberty (posthumous), orderRankWithinOrderOfLiberty, Officer]
-
A.
orderOf
Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
-
B.
confersOrder
Indicates that one entity formally bestows or grants an order, rank, or honorific distinction upon another entity.
-
C.
distributionOrder
Indicates the sequence or arrangement in which items or resources are distributed among recipients or locations.
-
D.
hasRankOrder
chosen
Indicates that one entity is ordered or positioned relative to others according to a specific ranking or sequence.
-
E.
foundingOrder
Indicates the chronological sequence in which entities were founded relative to one another.
- 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_69e0c455f3688190810bc96365791b0f |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee8139ce848190b812d6d07f1bdef8 |
completed | April 26, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e61639ee288190889ffd500d1260f6 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:48 p.m.