Triple
T9060985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Pas de Deux |
E217119
|
entity |
| Predicate | positionInPerformance |
P86740
|
FINISHED |
| Object | near the end of the ballet |
—
|
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: near the end of the ballet | Statement: [Grand Pas de Deux, positionInPerformance, near the end of the ballet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInPerformance Context triple: [Grand Pas de Deux, positionInPerformance, near the end of the ballet]
-
A.
playsInPosition
Indicates that an entity (typically a player) performs or operates in a specific role or position within a game, sport, or activity.
-
B.
positionInState
Indicates that one entity occupies or holds a specific position, role, or status within a particular state or condition of another entity.
-
C.
playingPosition
Indicates the specific role or position an individual occupies while participating in a game or sport.
-
D.
positionCoached
Indicates that one entity served as a coach for another entity in a specific position or role.
-
E.
positionInFormation
Indicates the relative place or role an entity occupies within an organized formation or arrangement.
- 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_69ca83d4425481909a319dab847724ec |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc7ecbb1e88190acdbfccdd975fac1 |
completed | April 1, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69cc65f881248190bfd220bb28a9fb5f |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc668ad3d881908a8a93a6a1d553e4 |
completed | April 1, 2026, 12:27 a.m. |
Created at: March 30, 2026, 7:11 p.m.