Triple
T10034537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | para-men |
E204930
|
entity |
| Predicate | conflictInStory |
P76396
|
FINISHED |
| Object | risk of universe destruction due to energy transfer |
—
|
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: risk of universe destruction due to energy transfer | Statement: [para-men, conflictInStory, risk of universe destruction due to energy transfer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictInStory Context triple: [para-men, conflictInStory, risk of universe destruction due to energy transfer]
-
A.
storyConflict
chosen
Indicates a relationship where a story contains or centers around a central problem, opposition, or tension that drives its plot.
-
B.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
C.
mainConflict
Indicates the primary opposing force, problem, or struggle that drives tension and narrative progression between entities or sides.
-
D.
conflictDescribedIn
Indicates that a particular conflict is documented, detailed, or discussed within a specified information source or description.
-
E.
conflictIntroduced
Indicates that a conflict has been newly created or brought into existence between the related entities.
- 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_69ca834d77188190ad645e33e8ca3200 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdce490ff08190963d841b05d150a7 |
completed | April 2, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8638508190b22acc65500ec7d6 |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:54 p.m.