Triple
T36152438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Max |
E1045625
|
entity |
| Predicate | settingOfImagination |
P141829
|
FINISHED |
| Object | island of monsters |
—
|
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: island of monsters | Statement: [Max, settingOfImagination, island of monsters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingOfImagination Context triple: [Max, settingOfImagination, island of monsters]
-
A.
settingOfFictionalLife
Indicates that a particular place or environment serves as the primary backdrop or context in which a fictional character’s life and experiences occur.
-
B.
settingOfMyth
Indicates that a location or environment serves as the backdrop or context in which a particular myth takes place.
-
C.
creativeUniverse
Indicates a relationship where an entity is responsible for originating, shaping, or imaginatively generating a universe or complete world.
-
D.
imaginaryWorld
chosen
Indicates a relationship where an entity exists within, belongs to, or is associated with a fictional or imagined world rather than the real one.
-
E.
settingOfAdventure
Indicates that a location or environment serves as the primary setting where an adventure takes place.
- 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_69f76e38903c8190a52887620f90aabe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: May 3, 2026, 4:08 p.m.