Triple
T20871422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M35A2 |
E513901
|
entity |
| Predicate | fuelSystemFeature |
P142180
|
FINISHED |
| Object | fuel density compensator |
—
|
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: fuel density compensator | Statement: [M35A2, fuelSystemFeature, fuel density compensator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuelSystemFeature Context triple: [M35A2, fuelSystemFeature, fuel density compensator]
-
A.
fuelSystem
Indicates a relationship where one entity serves as the fuel system (or part of it) that supplies, stores, or manages fuel for the operation of another entity.
-
B.
fuelCharacteristic
Indicates a relationship where a fuel is associated with one of its defining properties or qualities, such as composition, performance, or behavior.
-
C.
refuellingSystem
Indicates a system or mechanism used to supply fuel from one entity to another.
-
D.
fuelTankConfiguration
Indicates how a system’s fuel tanks are arranged, connected, or structured relative to one another.
-
E.
fuelCondition
Indicates the state or quality of fuel associated with an entity, such as its level, usability, or readiness for operation.
- F. None of above. chosen
Provenance (4 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_69e0b4f675cc8190b4e745225b62eb66 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c4649cf88190b3ad946576aa46aa |
completed | April 21, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:45 p.m.