Triple
T35015719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Farmworld Finn |
E1010047
|
entity |
| Predicate | causeOfWorldState |
P82638
|
FINISHED |
| Object | Lich’s unchecked destruction |
—
|
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: Lich’s unchecked destruction | Statement: [Farmworld Finn, causeOfWorldState, Lich’s unchecked destruction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfWorldState Context triple: [Farmworld Finn, causeOfWorldState, Lich’s unchecked destruction]
-
A.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
B.
causeStatus
chosen
Indicates that one entity brings about, initiates, or is responsible for a particular state or condition in another entity.
-
C.
causeDescribedAs
Indicates that one entity is described or characterized as the cause of another entity or event.
-
D.
causeInStory
Indicates that one event, action, or state functions as the cause of another within the narrative structure of a story.
-
E.
causeOfDisaster
Indicates that the subject is responsible for bringing about or triggering the specified disaster.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: May 3, 2026, 4:01 p.m.