Triple
T34162729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eudoros |
E876320
|
entity |
| Predicate | foughtAgainstSide |
P172646
|
FINISHED |
| Object | Trojans |
—
|
NE NERFINISHED |
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: Trojans | Statement: [Eudoros, foughtAgainstSide, Trojans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foughtAgainstSide Context triple: [Eudoros, foughtAgainstSide, Trojans]
-
A.
foughtAs
Indicates that an entity participated in a conflict or war in the capacity, role, or identity specified by another entity.
-
B.
foughtForFaction
Indicates that an entity actively participated in or supported a particular faction, typically in a conflict or struggle.
-
C.
laterFoughtAlongside
Indicates that two entities, who were previously in some other relationship or context, subsequently fought on the same side as allies in a conflict or battle.
-
D.
conflictSide
Indicates that an entity participates as a distinct party or faction on one side of a conflict or dispute.
-
E.
wasEnemyOf
chosen
Indicates that one entity regarded or interacted with another as an adversary or opponent, typically in a hostile or conflicting relationship.
- 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_69f349ac987481908a8e6053f665bc8b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fdedf708190ab68c2d567e086d0 |
completed | May 3, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:54 a.m.