Triple
T4320100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London 2012 Olympic beach volleyball tournament |
E96491
|
entity |
| Predicate | setsPerMatch |
P56213
|
FINISHED |
| Object | best of three sets |
—
|
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: best of three sets | Statement: [London 2012 Olympic beach volleyball tournament, setsPerMatch, best of three sets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setsPerMatch Context triple: [London 2012 Olympic beach volleyball tournament, setsPerMatch, best of three sets]
-
A.
usesNumberOfPlayersOnFieldPerTeam
Indicates that the relationship specifies or depends on how many players each team has on the field at a given time.
-
B.
groupStageMatchesPerTeam
Indicates the number of matches each team plays during the group stage of a competition.
-
C.
playoffMeetingsCount
Indicates the number of times the entities have faced each other in playoff competitions.
-
D.
totalMatchesPerSeason
Indicates the total number of matches associated with an entity within a single season.
-
E.
matchupFrequency
Indicates how often a particular pair or set of entities are matched or paired against each other within a given context or timeframe.
- 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_69b345422aac81909ddbadae437d122e |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35114ed2c8190949c5d8032d7b921 |
completed | March 12, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69b34f4bec888190987fc2631498b637 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3501834448190bedf775a80da4778 |
completed | March 12, 2026, 11:45 p.m. |
Created at: March 12, 2026, 11:12 p.m.