Triple
T10045129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aviron Bayonnais rugby union |
E207595
|
entity |
| Predicate | playsXVSide |
P91804
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Aviron Bayonnais rugby union, playsXVSide, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsXVSide Context triple: [Aviron Bayonnais rugby union, playsXVSide, yes]
-
A.
playType
Indicates the specific category or style of play or performance associated with an event or action.
-
B.
playsOn
Indicates that one entity participates or performs on a particular team, platform, or medium.
-
C.
playsOnSurface
Indicates that an entity performs or engages in an activity while being in contact with or supported by a particular surface.
-
D.
plays5On5
Indicates that the subject participates in a five-on-five game or match involving two teams of five players each.
-
E.
playIn
Indicates that an entity participates or performs in a particular event, context, or location (such as a game, match, 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_69ca835ad0608190b7c80b292da004f5 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcf62ecf081909c055171b78a883a |
completed | April 2, 2026, 2:07 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8d2280819089de27e57babd1f3 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8d9b888190b8067bd916dae773 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 8:56 p.m.