Triple
T36732636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Site B |
E907380
|
entity |
| Predicate | hasFictionalClimate |
P201884
|
FINISHED |
| Object | tropical |
—
|
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: tropical | Statement: [Site B, hasFictionalClimate, tropical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalClimate Context triple: [Site B, hasFictionalClimate, tropical]
-
A.
hasFictionalScope
Indicates that something pertains to, applies within, or is limited to a fictional or imagined context rather than real-world scope.
-
B.
hasFictionalForm
Indicates that an entity has a counterpart or representation that exists within a fictional or imaginary context.
-
C.
hasFictionalType
Indicates that an entity is associated with or classified under a particular type or category that is fictional rather than real.
-
D.
hasFictionalGenreCharacteristic
Indicates that something possesses a specific characteristic or attribute related to a fictional genre.
-
E.
hasFictionalEventType
Indicates that something is associated with, characterized by, or classified under a particular type or category of fictional event.
- F. None of above. chosen
Provenance (4 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_69f76e75aa6881909b844d00a3888ee5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a002e71bdc48190b922f2d3b362d259 |
completed | May 10, 2026, 7:06 a.m. |
| PD | Predicate disambiguation | batch_6a002e1a28708190b65f9e657c770bab |
completed | May 10, 2026, 7:04 a.m. |
| PDg | Predicate description generation | batch_6a002e706dfc8190bbf2bc230f537e83 |
completed | May 10, 2026, 7:06 a.m. |
Created at: May 3, 2026, 4:12 p.m.