Triple
T13502893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Constructors' Championship |
E320936
|
entity |
| Predicate | teamSizeRequirement |
P9344
|
FINISHED |
| Object | minimum two drivers |
—
|
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: minimum two drivers | Statement: [World Constructors' Championship, teamSizeRequirement, minimum two drivers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamSizeRequirement Context triple: [World Constructors' Championship, teamSizeRequirement, minimum two drivers]
-
A.
teamConstraint
Indicates a rule or limitation governing how entities can be grouped, associated, or operate together as a team.
-
B.
typicalTeamSize
Indicates the usual or most common number of members that make up a given team.
-
C.
clubSize
Indicates the number of members or participants in a given club.
-
D.
minimumNumberOfMembers
chosen
Indicates the smallest allowable or required number of members that must be present or involved in a given context or group.
-
E.
collaborationSize
Indicates the number of participants involved together in a given collaborative relationship or activity.
- F. None of above.
Provenance (3 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf50f4a48190a44fc537b78c32fd |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:43 p.m.