Triple
T13007818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cage of Death |
E322332
|
entity |
| Predicate | experienceSetting |
P56736
|
FINISHED |
| Object | urban wildlife attraction |
—
|
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: urban wildlife attraction | Statement: [Cage of Death, experienceSetting, urban wildlife attraction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: experienceSetting Context triple: [Cage of Death, experienceSetting, urban wildlife attraction]
-
A.
settingOfExperience
chosen
Indicates that a particular context, environment, or situation serves as the backdrop or circumstances in which an experience occurs.
-
B.
experienceFeature
Indicates that an entity undergoes, encounters, or makes use of a particular feature.
-
C.
experienceStyle
Indicates that one entity has or is associated with a particular manner, approach, or style in which an experience is delivered or undergone.
-
D.
experienceType
Indicates the specific kind or category of experience associated with an entity or event.
-
E.
providesExperienceOf
Indicates that one entity enables or delivers the experience of another entity to someone or something.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e9cf0108190b02f498c6ccc91f8 |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc153a081909d13a694993f074a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:48 p.m.