Triple
T15460819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leonnatus |
E371892
|
entity |
| Predicate | supportedFactionAfterAlexanderDeath |
P82209
|
FINISHED |
| Object | Macedonian regency |
—
|
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: Macedonian regency | Statement: [Leonnatus, supportedFactionAfterAlexanderDeath, Macedonian regency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedFactionAfterAlexanderDeath Context triple: [Leonnatus, supportedFactionAfterAlexanderDeath, Macedonian regency]
-
A.
hasOpposingFaction
Indicates that one faction stands in opposition or conflict to another faction.
-
B.
roleAfterAlexander
chosen
Indicates that one entity holds a role, position, or status that is defined or understood specifically in the context of the period after Alexander (typically Alexander the Great).
-
C.
rebellionAllies
Indicates that two or more entities are aligned as allies in a shared rebellion or uprising against a common authority or power.
-
D.
allyOfByzantines
Indicates a relationship where an entity served as an ally or cooperative partner of the Byzantine Empire.
-
E.
opposingAlliance
Indicates that two entities belong to rival or mutually opposed alliances or factions.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f17663c8190b995c7c3129c90d6 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:32 a.m.