Triple
T13007783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cage of Death |
E322332
|
entity |
| Predicate | usesEnclosureType |
P15848
|
FINISHED |
| Object | transparent enclosure |
—
|
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: transparent enclosure | Statement: [Cage of Death, usesEnclosureType, transparent enclosure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesEnclosureType Context triple: [Cage of Death, usesEnclosureType, transparent enclosure]
-
A.
hasEnclosures
chosen
Indicates that an entity possesses or contains one or more enclosing structures, spaces, or bounded areas associated with it.
-
B.
containsEnclave
Indicates that one region or territory fully surrounds and encloses another distinct region or territory as an enclave.
-
C.
usesElement
Indicates that one entity makes use of, incorporates, or depends on a specified element in its structure, function, or behavior.
-
D.
isInCabinet
Indicates that one entity serves as a member of the governing cabinet associated with another entity (such as a government or administration).
-
E.
hasEnclosureName
Indicates that an entity is associated with the specific name of an enclosure in which it is contained or housed.
- 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.