Triple
T26761326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Chief |
E674807
|
entity |
| Predicate | oftenEndangers |
P16824
|
FINISHED |
| Object | members of the Doom Patrol |
—
|
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: members of the Doom Patrol | Statement: [The Chief, oftenEndangers, members of the Doom Patrol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenEndangers Context triple: [The Chief, oftenEndangers, members of the Doom Patrol]
-
A.
endangerment
chosen
Indicates a relationship in which one entity exposes another to potential harm, risk, or danger.
-
B.
endangermentType
Indicates the specific way or manner in which one entity puts another at risk of harm, loss, or damage.
-
C.
dangerousWhen
Indicates that one entity becomes harmful, risky, or unsafe under the conditions or in the presence of another entity or situation.
-
D.
likelyEndangered
Indicates that an entity is at significant risk of becoming endangered in the near future based on current conditions or trends.
-
E.
isHazardTo
Indicates that one entity poses a potential source of danger, harm, or risk to another entity.
- 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_69eecda6e9dc81908452fab3ba17ed9b |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 27, 2026, 3:58 a.m.