Triple
T9486916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | optio |
E228784
|
entity |
| Predicate | secondInCommandOf |
P31581
|
FINISHED |
| Object | century |
—
|
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: century | Statement: [optio, secondInCommandOf, century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondInCommandOf Context triple: [optio, secondInCommandOf, century]
-
A.
secondSupremeLeader
Indicates that the subject is the second individual to hold the position of supreme leader of the object entity.
-
B.
secondLeader
chosen
Indicates that an entity serves as the second-ranking leader or deputy leader in relation to another entity.
-
C.
commanderAlsoServesAs
Indicates that the person who holds a commander role simultaneously fulfills one or more additional official roles or positions.
-
D.
otherMajorLeader
Indicates that one entity is a significant political or organizational leader distinct from the primary or main leader in a given context.
-
E.
firstSupremeLeader
Indicates that the subject is the first person to hold the position or title of supreme leader of the object entity.
- 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_69ca847424f081908180305555139f7a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd8051303881909566126a2688e41c |
completed | April 1, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69cca561e6b0819090aa795f3c3a2083 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:55 p.m.