Triple
T35016126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mushroom Island |
E1010057
|
entity |
| Predicate | worldStateContext |
P141265
|
FINISHED |
| Object | post-apocalyptic |
—
|
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: post-apocalyptic | Statement: [Mushroom Island, worldStateContext, post-apocalyptic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldStateContext Context triple: [Mushroom Island, worldStateContext, post-apocalyptic]
-
A.
hasWorldState
chosen
Indicates that an entity is associated with, or exists within, a particular overall configuration or condition of the world at a given time.
-
B.
worldDefinitionInContext
Indicates that a particular definition of a term or concept is specified as it applies within a given context or situation.
-
C.
bringsToWorldState
Indicates a relationship where an action or event causes a particular world state or condition to come into existence or be realized.
-
D.
regionContext
Indicates the broader geographic or spatial setting within which an entity, event, or relationship is situated or interpreted.
-
E.
stateStructureContext
Indicates the contextual framework or structural conditions of a state within which a given relationship or action occurs.
- 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_69fe7b1c506c8190869c1a22031e0571 |
completed | May 9, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69fe796b2bdc8190a86980d44008f875 |
completed | May 9, 2026, 12:01 a.m. |
Created at: May 3, 2026, 4:01 p.m.