Triple
T2358475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flying Pencil |
E47212
|
entity |
| Predicate | fuselageCharacteristic |
P21223
|
FINISHED |
| Object | slender fuselage |
—
|
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: slender fuselage | Statement: [Flying Pencil, fuselageCharacteristic, slender fuselage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuselageCharacteristic Context triple: [Flying Pencil, fuselageCharacteristic, slender fuselage]
-
A.
fuselageType
Indicates the specific structural or design category of an aircraft’s fuselage that an entity belongs to or uses.
-
B.
fuselageShape
chosen
Indicates the geometric form or contour of an object's fuselage, describing how its main body is shaped.
-
C.
fuselageDiameter
Indicates the diameter measurement of an aircraft’s fuselage in the described context.
-
D.
wingArea
Indicates the total surface area covered by an entity’s wing or wings.
-
E.
aerodynamicsFeature
Indicates that one entity possesses or is characterized by a specific aerodynamic property, component, or design feature affecting airflow and motion through air.
- 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_69a88a1a4a6081908645b0f2914521ab |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc71f767481908dfa9be209ea3c5a |
completed | March 7, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69abc599b92c819093d9e15d4437705d |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:55 p.m.