Triple
T38619964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarzan’s Jungle |
E936840
|
entity |
| Predicate | hasPrimarySettingElement |
P206584
|
FINISHED |
| Object | jungle canopy |
—
|
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: jungle canopy | Statement: [Tarzan’s Jungle, hasPrimarySettingElement, jungle canopy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimarySettingElement Context triple: [Tarzan’s Jungle, hasPrimarySettingElement, jungle canopy]
-
A.
hasSetting
Indicates that an entity takes place, occurs, or exists within a particular environment, context, or location.
-
B.
hasSettingBy
Indicates that something (such as a work, event, or scenario) has its contextual environment, location, or background defined or established by a particular agent or source.
-
C.
hasPrimaryLocationSetting
Indicates that an entity is associated with its main or default geographic or contextual location.
-
D.
hasPrimary
Indicates that one entity is designated as the main or most important instance (the primary) in relation to another entity.
-
E.
hasPrimarySection
Indicates that an entity is associated with or organized under a main or principal section within a larger structure or grouping.
- 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_69f76ed403208190b862dc795171353f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c85e308819083dd67b96f457659 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:32 p.m.