Triple
T4922161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iole |
E110489
|
entity |
| Predicate | indirectlyLeadsTo |
P18658
|
FINISHED |
| Object | Heracles' tragic death |
—
|
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: Heracles' tragic death | Statement: [Iole, indirectlyLeadsTo, Heracles' tragic death]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indirectlyLeadsTo Context triple: [Iole, indirectlyLeadsTo, Heracles' tragic death]
-
A.
canLeadTo
chosen
Indicates that one entity, condition, or event has the potential to cause, result in, or bring about another.
-
B.
hasStepsLeadingTo
Indicates that one location or object is connected to another by a set of steps or a staircase leading toward it.
-
C.
flowsTo
Indicates that something moves or is directed from one location or entity toward and into another, typically in a continuous or channel-like manner.
-
D.
indirectImpactOn
Indicates that one entity affects another entity’s state, condition, or outcome through one or more intermediate factors rather than through a direct interaction.
-
E.
followsFrom
Indicates that one fact, event, or state logically or causally results from, is implied by, or comes as a consequence of another.
- 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_69bd4413f9908190afcff44d7929cc4c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ffc2ab08190992db2400562bcee |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3421588190ab08e92b9558042e |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:30 p.m.