Triple
T9841715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baithak Gana |
E239241
|
entity |
| Predicate | performerPosition |
P90285
|
FINISHED |
| Object | 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: seated | Statement: [Baithak Gana, performerPosition, seated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performerPosition Context triple: [Baithak Gana, performerPosition, seated]
-
A.
positionInPerformance
Indicates the specific ordering or placement of an entity within a performance or sequence of performed elements.
-
B.
playsInPosition
Indicates that an entity (typically a player) performs or operates in a specific role or position within a game, sport, or activity.
-
C.
performerOn
Indicates that an entity serves as the performer or executing agent of an action, event, or work associated with another entity.
-
D.
coPerformer
Indicates that two or more entities jointly perform the same act or participate together in the same performance.
-
E.
performerType
Indicates the role or category of performer responsible for carrying out an action or participating in an event.
- 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_69ca84e3f0c48190ada72a65ebd50efd |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb34e3420819084bb31170e643cd0 |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e57cac8190914bb5ae608a6e0e |
completed | April 1, 2026, 11:39 a.m. |
| PDg | Predicate description generation | batch_69cd06ace53081909b5f81f382f6591e |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:33 p.m.