Triple
T1414262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orpheus |
E31875
|
entity |
| Predicate | conditionViolated |
P2111
|
FINISHED |
| Object | looked back at Eurydice |
—
|
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: looked back at Eurydice | Statement: [Orpheus, conditionViolated, looked back at Eurydice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conditionViolated Context triple: [Orpheus, conditionViolated, looked back at Eurydice]
-
A.
violatedPrinciple
chosen
Indicates that an entity has broken, disregarded, or acted contrary to a specified rule, norm, or guiding principle.
-
B.
failsWhen
Indicates that a particular action, process, or condition does not succeed under the specified circumstances or triggers.
-
C.
isBrokenBy
Indicates that one entity causes another entity to become damaged, nonfunctional, or destroyed.
-
D.
conditions
Indicates that one entity specifies or imposes requirements, constraints, or circumstances that must be satisfied or hold true for another entity or situation.
-
E.
raisesIssue
Indicates that one entity brings up, reports, or formally submits a concern, problem, or topic for attention to another entity or system.
- 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_69a49919a994819086528951bc224775 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3e5f9d08190861206934cd71fd8 |
completed | March 1, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69a4bf060b0081909ba00e6ac093a28b |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.