Triple
T8227224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gnaeus Pompeius Strabo |
E192201
|
entity |
| Predicate | held rank |
P52914
|
FINISHED |
| Object | praetor |
—
|
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: praetor | Statement: [Gnaeus Pompeius Strabo, held rank, praetor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: held rank Context triple: [Gnaeus Pompeius Strabo, held rank, praetor]
-
A.
typicallyHoldsRank
Indicates that an entity is most commonly or usually associated with holding a particular rank or level in a hierarchy.
-
B.
militaryRank
Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
-
C.
firstHolderMilitaryRank
Indicates that the subject entity holds or held the earliest or initial military rank associated with the referenced entity.
-
D.
honorificRank
Indicates that one entity holds a formal title or honorific status in relation to another entity.
-
E.
isMilitaryRank
chosen
Indicates that one entity holds a specific position or level within a formal military hierarchy in relation to 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_69ca82db5b90819085d1ad7c2e27bfcc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb77fdcb048190868ea4995b020a37 |
completed | March 31, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69cb36af41e081909dee92b9bc4947f1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:46 p.m.