Triple
T1361193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIRST Tech Challenge |
E29101
|
entity |
| Predicate | robotPlatform |
P17735
|
FINISHED |
| Object | kit-based modular robot system |
—
|
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: kit-based modular robot system | Statement: [FIRST Tech Challenge, robotPlatform, kit-based modular robot system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: robotPlatform Context triple: [FIRST Tech Challenge, robotPlatform, kit-based modular robot system]
-
A.
winningRobot
Indicates that a robot is the one that has won a specified competition, contest, or task.
-
B.
platforms
Indicates that one entity provides or serves as a base, medium, or environment that supports the operation, distribution, or presentation of another entity.
-
C.
numberOfMotors
Indicates the quantity of motors associated with or used by an entity.
-
D.
mobilityComponent
Indicates that one entity functions as a mobility-related component or module that enables or affects the movement capabilities of another entity.
-
E.
consideredPlatform
chosen
Indicates that one entity is regarded or treated as a platform (e.g., a base, medium, or environment) for another entity 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_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.