Triple
T35382203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lippisch P.13a |
E1022679
|
entity |
| Predicate | fuelRationale |
P101297
|
FINISHED |
| Object | coal chosen to save liquid fuel |
—
|
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: coal chosen to save liquid fuel | Statement: [Lippisch P.13a, fuelRationale, coal chosen to save liquid fuel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuelRationale Context triple: [Lippisch P.13a, fuelRationale, coal chosen to save liquid fuel]
-
A.
fuelChoiceRationale
chosen
Indicates the reasoning or justification behind selecting a particular type of fuel over alternatives.
-
B.
fuelTransport
Indicates the transfer or conveyance of fuel from one location or entity to another.
-
C.
fuelCondition
Indicates the state or quality of fuel associated with an entity, such as its level, usability, or readiness for operation.
-
D.
fuelEffect
Indicates the influence or impact that a given fuel has on a process, system, or outcome.
-
E.
fuelForm
Indicates the physical or chemical form in which a fuel exists or is supplied (e.g., liquid, gas, solid).
- 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_69f76df28d8c819089f2c5799fe7d079 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.