Triple
T36731876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Αἴας |
E907362
|
entity |
| Predicate | fightsAgainstSide |
P188149
|
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: [Αἴας, fightsAgainstSide, Trojans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fightsAgainstSide Context triple: [Αἴας, fightsAgainstSide, Trojans]
-
A.
fightsUsing
Indicates that one entity engages in combat or conflict by employing another entity as its weapon, tool, or method of fighting.
-
B.
forcesSide2
Indicates that one entity compels or coerces another entity to take or remain on a particular side or position in a situation or conflict.
-
C.
diesFighting
Indicates that an entity dies as a direct result of engaging in a fight or combat.
-
D.
fightingPreference
Indicates a relationship where one entity has a favored way, style, or choice of engaging in fights or combat relative to others.
-
E.
opposingCommanderSide
Indicates that one commander is on the opposing or enemy side relative to another commander in a conflict or confrontation.
- F. None of above. chosen
Provenance (4 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_69f76e75aa6881909b844d00a3888ee5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fba28684208190921694f23e350c3b |
completed | May 6, 2026, 8:20 p.m. |
Created at: May 3, 2026, 4:12 p.m.