Triple
T6753391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elateia |
E154392
|
entity |
| Predicate | promptedEvent |
P693
|
FINISHED |
| Object | Athenian alliance with Thebes against Philip II |
—
|
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: Athenian alliance with Thebes against Philip II | Statement: [Elateia, promptedEvent, Athenian alliance with Thebes against Philip II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promptedEvent Context triple: [Elateia, promptedEvent, Athenian alliance with Thebes against Philip II]
-
A.
triggered
chosen
Indicates that one entity causes an event, action, or process involving another entity to start or occur.
-
B.
eventCommanded
Indicates that one entity issued an order or directive for another entity to carry out a specific event or action.
-
C.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
-
D.
basedOnEvent
Indicates that something is derived from, influenced by, or determined in reference to a specific event.
-
E.
typicalEvent
Indicates that the associated event is a common, characteristic, or prototypical occurrence for the given entity or situation.
- 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_69c6880fd5808190be684854081e27dd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d327e37081909d576e6eff9eec97 |
completed | March 27, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69c6d09227108190b253b91967831a85 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:11 p.m.