Triple
T33095331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flagon |
E846892
|
entity |
| Predicate | subjectAircraftPropulsion |
P67482
|
FINISHED |
| Object | jet-powered |
—
|
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: jet-powered | Statement: [Flagon, subjectAircraftPropulsion, jet-powered]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectAircraftPropulsion Context triple: [Flagon, subjectAircraftPropulsion, jet-powered]
-
A.
propulsion
Indicates a relationship where one entity provides the driving force or thrust that moves another entity forward or keeps it in motion.
-
B.
aircraftPowerplantType
chosen
Indicates the type or category of powerplant (e.g., engine or propulsion system) used by an aircraft.
-
C.
aircraftEngineType
Indicates the specific type or classification of engine that an aircraft uses.
-
D.
aircraft
Indicates that an entity is an aircraft or functions in the role of an aircraft in the described context.
-
E.
primaryAircraftPowered
Indicates that one entity serves as the main aircraft whose operation is enabled or driven by the power source or propulsion system represented by the other entity.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: May 1, 2026, 1:26 a.m.