Triple
T29390840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regular Category (World Robot Olympiad) |
E745364
|
entity |
| Predicate | allowsTeamSize |
P55075
|
FINISHED |
| Object | 2–3 students per team |
—
|
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: 2–3 students per team | Statement: [Regular Category (World Robot Olympiad), allowsTeamSize, 2–3 students per team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsTeamSize Context triple: [Regular Category (World Robot Olympiad), allowsTeamSize, 2–3 students per team]
-
A.
teamSizeVariantOf
Indicates that one entity represents a variation of another entity specifically in terms of team size configuration or composition.
-
B.
typicalTeamSize
Indicates the usual or most common number of members that make up a given team.
-
C.
squadSizeType
Indicates the type or classification of a squad based on its size.
-
D.
teamSizeFormat
Indicates how the size of a team is represented or formatted (e.g., as a number, range, or categorized label).
-
E.
teamConstraint
chosen
Indicates a rule or limitation governing how entities can be grouped, associated, or operate together as a team.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: April 28, 2026, 2:42 p.m.