Triple
T13351291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spooky Island |
E318073
|
entity |
| Predicate | hasInhabitantsInStory |
P97696
|
FINISHED |
| Object | park employees |
—
|
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: park employees | Statement: [Spooky Island, hasInhabitantsInStory, park employees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInhabitantsInStory Context triple: [Spooky Island, hasInhabitantsInStory, park employees]
-
A.
hasAllyInStory
Indicates that one entity is portrayed as an ally or supportive partner of another entity within the context of a specific story or narrative.
-
B.
appearsInShortStoryBy
Indicates that one entity is a character, element, or subject that appears within a short story authored by another entity.
-
C.
hasSiblingInStory
Indicates that one character in a narrative has at least one sibling who also appears within the same story.
-
D.
hasFictionalInhabitants
chosen
Indicates that a place or setting is inhabited by fictional or imaginary beings.
-
E.
hasFandomWithinStory
Indicates that within the narrative of a story, one entity is a fan or admirer of another entity (such as a character, group, or work) that exists inside that same story world.
- 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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99e8c2f1c819094f0970f35f18afa |
completed | April 11, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69d98f6fd8bc819086dddb6f376efa57 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:31 p.m.