Triple
T35032425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opsikion Theme |
E1010815
|
entity |
| Predicate | laterCommandTitle |
P39450
|
FINISHED |
| Object | stratēgos of the Opsikion |
—
|
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: stratēgos of the Opsikion | Statement: [Opsikion Theme, laterCommandTitle, stratēgos of the Opsikion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterCommandTitle Context triple: [Opsikion Theme, laterCommandTitle, stratēgos of the Opsikion]
-
A.
laterTitleOfCommander
chosen
Indicates that one title represents a later-held command position of the same commander who previously held another title.
-
B.
laterTitleHolder
Indicates that one entity is a subsequent holder of a particular title or position previously held by another entity.
-
C.
laterNamed
Indicates that an entity was given a new name at a later time, linking its original identity to its subsequent name.
-
D.
associatedCommand
Indicates a relationship where one entity is linked to, or meant to be used with, a particular command or set of commands.
-
E.
laterTask
Indicates that one task occurs after another in time, representing a temporal ordering where the first task precedes the laterTask.
- 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_69f76dcea02c81908542a223f6d5059f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a004c41f13c8190bc47daf6a5ca3949 |
completed | May 10, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_6a004bce3e3081909b35ae5b3bf2b35e |
completed | May 10, 2026, 9:11 a.m. |
Created at: May 3, 2026, 4:01 p.m.