Triple
T18696454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Antiphates |
E457126
|
entity |
| Predicate | firstAttacks |
P121575
|
FINISHED |
| Object | one of Odysseus’s scouts |
—
|
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: one of Odysseus’s scouts | Statement: [King Antiphates, firstAttacks, one of Odysseus’s scouts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstAttacks Context triple: [King Antiphates, firstAttacks, one of Odysseus’s scouts]
-
A.
enemyAtFirst
Indicates that two entities initially regard or treat each other as enemies when they first meet or interact.
-
B.
numberOfAttacks
Indicates the count of distinct attack events associated with a given entity or interaction.
-
C.
firstFight
Indicates that the referenced event is the initial instance in which the involved entities engaged in a fight or combat with each other.
-
D.
causeOfDefeatInFirstAttack
Indicates the specific factor or event that led to an entity’s defeat during the initial attack.
-
E.
firstStruck
chosen
Indicates that one entity was the initial party to hit, attack, or make physical contact with another in a conflict or interaction.
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e562e8bc408190ab41b3c21003c249 |
completed | April 19, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.