Triple
T23480985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robby the Robot |
E570402
|
entity |
| Predicate | propHeight |
P9788
|
FINISHED |
| Object | about 7 feet |
—
|
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: about 7 feet | Statement: [Robby the Robot, propHeight, about 7 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propHeight Context triple: [Robby the Robot, propHeight, about 7 feet]
-
A.
hasHeight
chosen
Indicates that one entity possesses a specific vertical measurement or stature.
-
B.
platformHeight
Indicates the vertical distance or elevation of a platform relative to a defined reference level.
-
C.
typicalHeight
Indicates the usual or characteristic height associated with an entity, such as a person, object, or species.
-
D.
heightContext
Indicates a contextual or situational relationship that specifies how an entity’s height is defined, measured, or interpreted in a particular setting or frame of reference.
-
E.
plannedHeight
Indicates the intended or designed vertical size or elevation that something is planned to have.
- 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_69e245af8a88819084f2704f6d265a92 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a75002008190b02fbffd94e5e8b1 |
completed | April 29, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:03 p.m.