Triple
T31391396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | dilruba |
E800739
|
entity |
| Predicate | hasPerformancePosture |
P192653
|
FINISHED |
| Object | played seated |
—
|
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: played seated | Statement: [dilruba, hasPerformancePosture, played seated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformancePosture Context triple: [dilruba, hasPerformancePosture, played seated]
-
A.
hasPerformanceProfile
Indicates that an entity is associated with a specific performance profile that characterizes its performance attributes or behavior.
-
B.
hasPerformanceElement
Indicates that one entity includes, contains, or is associated with a specific performance-related component or element.
-
C.
hasPerformanceConvention
Indicates that there is an agreed-upon set of rules, norms, or standards governing how a particular performance or activity should be carried out.
-
D.
hasPerformanceContext
Indicates that an entity is associated with a specific performance-related situation, setting, or set of conditions under which it operates or is evaluated.
-
E.
hasPerformanceLocation
Indicates that an event, performance, or show takes place at a specified location or venue.
- F. None of above. chosen
Provenance (4 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_69f224e9d7048190b0cc20f9071bd3e4 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
| PDg | Predicate description generation | batch_69fd231bdd108190900369e07c854e95 |
completed | May 7, 2026, 11:41 p.m. |
Created at: April 29, 2026, 9:19 p.m.