Triple
T18696399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telepylus harbor |
E457125
|
entity |
| Predicate | eventOccursAt |
P58129
|
FINISHED |
| Object | attack on Odysseus’s fleet by the Laestrygonians |
—
|
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: attack on Odysseus’s fleet by the Laestrygonians | Statement: [Telepylus harbor, eventOccursAt, attack on Odysseus’s fleet by the Laestrygonians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventOccursAt Context triple: [Telepylus harbor, eventOccursAt, attack on Odysseus’s fleet by the Laestrygonians]
-
A.
eventOccurredAt
chosen
Indicates that a particular event took place at a specific time or location.
-
B.
eventDateAtLocation
Indicates that a specific event occurs on a particular date at a given location.
-
C.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
-
D.
scheduledDestinationAtTimeOfEvent
Indicates that an entity was planned or expected to be at a specific destination at the time a particular event occurred.
-
E.
onOccasionOf
Indicates that one event, action, or state occurs in connection with, or is triggered by, a particular occasion or special event.
- 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_69e562e775408190996b4c613b83f185 |
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.