Triple
T7379175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pirithous |
E170202
|
entity |
| Predicate | causeOfBattle |
P61068
|
FINISHED |
| Object | attempted abduction of Lapith women by Centaurs |
—
|
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: attempted abduction of Lapith women by Centaurs | Statement: [Pirithous, causeOfBattle, attempted abduction of Lapith women by Centaurs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfBattle Context triple: [Pirithous, causeOfBattle, attempted abduction of Lapith women by Centaurs]
-
A.
hasCauseOfConflict
chosen
Indicates a relationship where one entity is the source or reason for a conflict involving another entity.
-
B.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
-
C.
causeOfPoliticalConflict
Indicates that one entity is the source or reason for a political conflict involving another entity.
-
D.
battleWasPartOf
Indicates that a specific battle occurred as a component or phase within a larger military campaign, war, or conflict.
-
E.
battleAlsoKnownAs
Indicates that a particular battle is known by an alternative name or names.
- 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_69c68a5d0ed08190b6d361e68f813330 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f1c4ad0081909386fbef9f61ae4c |
completed | March 27, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69c6f02ee3e08190a7a00c981129b22c |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:08 p.m.