Triple
T28147674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiswas |
E714527
|
entity |
| Predicate | notableSketchOrSegment |
P3574
|
FINISHED |
| Object | The Cage |
—
|
NE NERFINISHED |
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: The Cage | Statement: [Tiswas, notableSketchOrSegment, The Cage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSketchOrSegment Context triple: [Tiswas, notableSketchOrSegment, The Cage]
-
A.
hasNotableSketch
Indicates that an entity is associated with a sketch that is considered notable or significant in some context.
-
B.
notableSegmentType
Indicates that a particular segment or portion of something is classified as being of notable or special significance by its type.
-
C.
sketchType
Indicates the specific kind or category of sketch associated with an entity or action.
-
D.
notableSurface
Indicates that one entity is a surface or exterior of particular significance or prominence in relation to another entity.
-
E.
hasNotableSegment
chosen
Indicates that an entity includes or contains a specific segment, part, or portion that is considered notable or significant in some way.
- 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_69efd6b033208190bf74f80a147e2092 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_6a008c77d4dc8190b342d7407eaf48fa |
completed | May 10, 2026, 1:47 p.m. |
| PD | Predicate disambiguation | batch_6a008c18531c8190bbe883b73e6d023f |
completed | May 10, 2026, 1:46 p.m. |
Created at: April 27, 2026, 9:57 p.m.