Triple
T13119529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Leaf |
E311685
|
entity |
| Predicate | flightMechanic |
P108141
|
FINISHED |
| Object | requires running to build P-Meter |
—
|
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: requires running to build P-Meter | Statement: [Super Leaf, flightMechanic, requires running to build P-Meter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flightMechanic Context triple: [Super Leaf, flightMechanic, requires running to build P-Meter]
-
A.
flightEngineer
Indicates that one entity serves as a flight engineer for another entity (such as a mission, aircraft, or crew).
-
B.
flightDeckFeature
Indicates that one entity is a feature, component, or element that is part of or present on the flight deck of another entity.
-
C.
aircraft
Indicates that an entity is an aircraft or functions in the role of an aircraft in the described context.
-
D.
flightTesting
Indicates the process of evaluating and validating an aircraft or aerospace system’s performance, safety, and functionality through controlled test flights.
-
E.
wingFunction
Indicates the functional role or purpose that a wing serves in enabling certain actions or capabilities.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98196e69081909111407ee3d9f08e |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98041a3548190a05ddd83dbb660fa |
completed | April 10, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d98134df64819084a5674f9475dcc2 |
completed | April 10, 2026, 11:01 p.m. |
Created at: April 9, 2026, 9:06 p.m.