Triple
T21085502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balinese culture |
E519476
|
entity |
| Predicate | hasTraditionalTheatre |
P102603
|
FINISHED |
| Object | topeng mask theatre |
—
|
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: topeng mask theatre | Statement: [Balinese culture, hasTraditionalTheatre, topeng mask theatre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalTheatre Context triple: [Balinese culture, hasTraditionalTheatre, topeng mask theatre]
-
A.
hasAncientTheatre
Indicates that one entity possesses or contains an ancient theatre as a notable feature or component.
-
B.
hasMunicipalTheatre
Indicates that a place or administrative entity possesses or contains a municipal theatre as one of its facilities.
-
C.
partOfHistoricalTheater
Indicates that one entity is a component, section, or feature belonging to a historical theater.
-
D.
hasTheatricalStaging
Indicates that something (such as a work or event) is presented or realized through a theatrical staging or performance.
-
E.
hasStageTradition
chosen
Indicates that an entity is associated with, follows, or embodies a particular stage or theatrical performance tradition.
- 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_69e0b507dd9081908fb8bfcbef4c8b46 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e709498fc081908d92a93e8678c140 |
completed | April 21, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:50 p.m.