Triple
T1361226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIRST Tech Challenge |
E29101
|
entity |
| Predicate | robotSizeConstraint |
P8078
|
FINISHED |
| Object | fits within an 18-inch cube at start of match |
—
|
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: fits within an 18-inch cube at start of match | Statement: [FIRST Tech Challenge, robotSizeConstraint, fits within an 18-inch cube at start of match]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: robotSizeConstraint Context triple: [FIRST Tech Challenge, robotSizeConstraint, fits within an 18-inch cube at start of match]
-
A.
heightRestriction
chosen
Indicates that there is a limit or constraint on how tall an entity is allowed or required to be in a given context.
-
B.
includesSizeRange
Indicates that one entity specifies or covers a particular range of sizes associated with another entity.
-
C.
restrictedArmySizeOf
Indicates that one entity imposes a limitation or cap on the allowable size of another entity’s army.
-
D.
weightLimitInKilograms
Indicates the maximum allowable weight for something, expressed in kilograms.
-
E.
bodySize
Indicates the relative physical magnitude or scale of an entity’s body, such as how large or small it is.
- 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_69a498d77abc8190913bf57e5f51d2c4 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c2b2fb448190bef31375169b4666 |
completed | March 1, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69a4bef945c08190a027472fdd695ea5 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:57 p.m.