Triple
T38092388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BEAM |
E951147
|
entity |
| Predicate | diameterStowed |
P124635
|
FINISHED |
| Object | about 2.36 meters |
—
|
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 2.36 meters | Statement: [BEAM, diameterStowed, about 2.36 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diameterStowed Context triple: [BEAM, diameterStowed, about 2.36 meters]
-
A.
bodyDiameter
chosen
Indicates the measurement of how wide an object's body is across its broadest cross-section.
-
B.
coreStageDiameter
Indicates the diameter measurement of the central or primary stage of an object or system.
-
C.
shellDiameter
Indicates the diameter measurement of a shell, typically specifying the distance across it at its widest point.
-
D.
mountDiameter
Indicates the size of the circular interface where one component is mounted onto another, typically measured as the diameter of the mounting point or opening.
-
E.
trackDiameter
Indicates the diameter measurement of a track, typically specifying the width across its circular or rounded layout.
- 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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:21 p.m.