Triple
T36732637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Site B |
E907380
|
entity |
| Predicate | hasFictionalTerrain |
P116836
|
FINISHED |
| Object | dense jungle |
—
|
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: dense jungle | Statement: [Site B, hasFictionalTerrain, dense jungle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalTerrain Context triple: [Site B, hasFictionalTerrain, dense jungle]
-
A.
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.
-
B.
hasFictionalLandmark
Indicates that one entity includes, features, or is associated with a landmark that is fictional rather than real.
-
C.
hasFictionalSettingElement
chosen
Indicates that something includes or is associated with a specific element or component of a fictional setting.
-
D.
hasFictionalGeographicIdentity
Indicates that an entity is associated with a geographic location that is fictional rather than real.
-
E.
hasFictionalWorldType
Indicates that an entity is associated with, set in, or characterized by a particular type or category of fictional 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_69f76e75aa6881909b844d00a3888ee5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a002f0839fc8190a874d3b0d0826d7e |
completed | May 10, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_6a002eae7b6481909974b321e2789b7e |
completed | May 10, 2026, 7:07 a.m. |
Created at: May 3, 2026, 4:12 p.m.