Triple
T19190072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XLR99-RM-1 |
E469809
|
entity |
| Predicate | vehicleTypePowered |
P1776
|
FINISHED |
| Object | experimental aircraft |
—
|
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: experimental aircraft | Statement: [XLR99-RM-1, vehicleTypePowered, experimental aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vehicleTypePowered Context triple: [XLR99-RM-1, vehicleTypePowered, experimental aircraft]
-
A.
poweredVehicleFamily
Indicates that one vehicle is part of a family or group of vehicles that share a common powered (motorized) design or platform.
-
B.
vehicleType
chosen
Indicates the specific kind or category of vehicle associated with an entity (e.g., car, bus, bicycle).
-
C.
motorizedUse
Indicates that an entity is used or operated by means of a motor or engine, rather than by human or animal power.
-
D.
vehicleEligibility
Indicates whether a given vehicle satisfies the required conditions or criteria to be considered eligible for a specified purpose or program.
-
E.
hasElectricMotor
Indicates that an entity is equipped with, contains, or uses an electric motor as part of its operation or structure.
- 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_69d8dd0ad9088190a173b32657ae2e7a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f8a16e20819080baa5112f000b41 |
completed | April 20, 2026, 9:57 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:07 p.m.