Triple
T4065154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ingenuity helicopter |
E86306
|
entity |
| Predicate | rotorDiameterMeters |
P22940
|
FINISHED |
| Object | 1.2 |
—
|
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: 1.2 | Statement: [Ingenuity helicopter, rotorDiameterMeters, 1.2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rotorDiameterMeters Context triple: [Ingenuity helicopter, rotorDiameterMeters, 1.2]
-
A.
rotorDiameter
chosen
Indicates the relationship where a rotor is associated with a specific measurement representing the diameter of its circular span.
-
B.
fuselageDiameter
Indicates the diameter measurement of an aircraft’s fuselage in the described context.
-
C.
fairingDiameter
Indicates the diameter measurement of a payload fairing used to enclose or protect an object.
-
D.
shaftDiameterAtBase
Indicates the diameter measurement of a shaft specifically at its base portion.
-
E.
impactorDiameter
Indicates the size of the object that impacts another body, typically measured as the diameter of the impacting body.
- 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_69aed93c69208190a4efac0efe3cd69b |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefd0bdea48190805a79515ee92709 |
completed | March 9, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69aef90438908190a005b08ba271eacf |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:38 p.m.