Triple
T36554632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sumatran Rat-Monkey |
E901667
|
entity |
| Predicate | hasFictionalHabitat |
P47688
|
FINISHED |
| Object | remote tropical island |
—
|
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: remote tropical island | Statement: [Sumatran Rat-Monkey, hasFictionalHabitat, remote tropical island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalHabitat Context triple: [Sumatran Rat-Monkey, hasFictionalHabitat, remote tropical island]
-
A.
hasFictionalInhabitants
Indicates that a place or setting is inhabited by fictional or imaginary beings.
-
B.
hasSpeciesInFiction
Indicates that a fictional work or universe features a particular species as part of its narrative or setting.
-
C.
hasFictionalLocation
Indicates that an entity is associated with, set in, or takes place within a location that exists only in fiction rather than in the real world.
-
D.
residesInFictionalLocation
chosen
Indicates that an entity lives or is based in a location that is explicitly fictional or imaginary.
-
E.
hasFictionalEstablishmentType
Indicates that an establishment is associated with a particular type or category of fictional setting or institution.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a00233e2170819084bee0c8f74cc1a4 |
completed | May 10, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_6a0022943fd08190b73007f080d5971d |
completed | May 10, 2026, 6:15 a.m. |
Created at: May 3, 2026, 4:11 p.m.