Triple
T35805508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doom |
E1035091
|
entity |
| Predicate | laterTurnedFace |
P202440
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Doom, laterTurnedFace, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterTurnedFace Context triple: [Doom, laterTurnedFace, true]
-
A.
turnedFace
Indicates that one entity directed or rotated its face toward another entity or specific direction.
-
B.
turnedFaceAndHeelMultipleTimes
Indicates repeatedly reversing one’s stance or allegiance, switching back and forth between opposing sides multiple times.
-
C.
turnedHeel
Indicates that an entity abruptly reversed direction or changed course, often implying a sudden shift in stance or behavior.
-
D.
mayFace
Indicates that an entity is likely or permitted to encounter, experience, or be subjected to another entity or situation.
-
E.
faceExpression
Indicates the specific facial expression an entity is displaying, capturing its visible emotional or expressive state.
- 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_69f76e169bd081909f16cd8c9ee7870c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a007fc9d9688190af411d5841af34be |
completed | May 10, 2026, 12:53 p.m. |
| PD | Predicate disambiguation | batch_6a007f64813081909a2950336402073b |
completed | May 10, 2026, 12:51 p.m. |
| PDg | Predicate description generation | batch_6a007fc8f9f88190b78cd2ef3fc9c6fc |
completed | May 10, 2026, 12:53 p.m. |
Created at: May 3, 2026, 4:06 p.m.