Triple
T22620610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CF6-80A |
E558265
|
entity |
| Predicate | intendedMounting |
P57768
|
FINISHED |
| Object | underwing pylon |
—
|
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: underwing pylon | Statement: [CF6-80A, intendedMounting, underwing pylon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedMounting Context triple: [CF6-80A, intendedMounting, underwing pylon]
-
A.
mountingLocation
Indicates the physical position or surface on which something is attached, fixed, or installed.
-
B.
trainMounting
Indicates a relationship where an entity is boarding or getting onto a train.
-
C.
mountingInterface
chosen
Indicates that one entity serves as the surface, structure, or connection point onto which another entity is mounted or attached.
-
D.
intendedInstallation
Indicates that one entity is meant or planned to be installed in, on, or as part of another entity or environment.
-
E.
intendedWith
Indicates that one entity is the planned or desired target, recipient, or context for the use or application of another 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_69e24545a8e08190bfa7482a2c725ff1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f16e383b048190a432c540185916d0 |
completed | April 29, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69ee62855558819080da946c7b35a160 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 3 p.m.