Triple
T26188054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | duitara |
E654882
|
entity |
| Predicate | playingContext |
P32813
|
FINISHED |
| Object | public performances |
—
|
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: public performances | Statement: [duitara, playingContext, public performances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playingContext Context triple: [duitara, playingContext, public performances]
-
A.
playIn
chosen
Indicates that an entity participates or performs in a particular event, context, or location (such as a game, match, or venue).
-
B.
playCharacteristic
Indicates that one entity exhibits a notable feature, style, or quality in the way it plays or performs something.
-
C.
playerControl
Indicates that one entity (typically a player) has control or command over another entity or object within a system or environment.
-
D.
play
Indicates that an entity engages in a recreational, performative, or competitive activity, often involving a game, sport, or musical performance, typically with another entity or object.
-
E.
playSource
Indicates that an entity serves as the origin or provider from which a play or playback action is initiated.
- 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_69ee5b469bc081908fe486453fdad810 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60c9f766081908b295347619baf89 |
completed | May 2, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 8:43 p.m.