Triple
T16234383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 100 metres – Beijing 2008 |
E394065
|
entity |
| Predicate | maximumAthletesPerNOC |
P122268
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [100 metres – Beijing 2008, maximumAthletesPerNOC, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumAthletesPerNOC Context triple: [100 metres – Beijing 2008, maximumAthletesPerNOC, 3]
-
A.
typicalNumberOfAthletes
Indicates the usual or average number of athletes associated with or participating in a given context, event, or entity.
-
B.
qualificationSpotsForOlympics
Indicates the number of available qualification positions that grant entry to the Olympic Games.
-
C.
numberOfMemberNOCs
Indicates the total count of National Olympic Committees (NOCs) that are members of a given organization or group.
-
D.
capacityDuringOlympics
Indicates the seating or usage capacity of a venue, facility, or service specifically during the Olympic Games period.
-
E.
expectedNumberOfAthletes
Indicates the anticipated or planned count of athletes expected to participate in a given context or 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_69d87f204df88190a8f88923decf9835 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e23d2be2f881908ec2483507cb0b00 |
completed | April 17, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69e219ee6f6481909663b388dc99770a |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:04 a.m.