Triple
T24051269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carnival! |
E595663
|
entity |
| Predicate | hasPuppetry |
P92902
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Carnival!, hasPuppetry, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPuppetry Context triple: [Carnival!, hasPuppetry, yes]
-
A.
performedPuppetryFor
Indicates that one entity carried out a puppetry performance for the benefit, entertainment, or purpose of another entity.
-
B.
hasPuppetCharacter
chosen
Indicates that one entity features, includes, or is associated with a particular puppet character as part of its content or composition.
-
C.
hasBlackBoxTheatre
Indicates that one entity possesses or includes a black box theatre as part of its facilities or features.
-
D.
hasDramaticProduction
Indicates that an entity is associated with or features a specific dramatic production (such as a play, performance, or staged work).
-
E.
theaterProduction
Indicates a relationship where a theatrical work is produced or staged, typically linking the production event to the play, venue, or organizing entity.
- 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_69e288c184b081909f1f1751fb8e299a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d9d1527c8190a4cd30bb1988a263 |
completed | April 29, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:20 p.m.