Triple
T35614571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VC-137C |
E1029129
|
entity |
| Predicate | airframeSAM26000 |
P183807
|
FINISHED |
| Object | first VC-137C built |
—
|
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: first VC-137C built | Statement: [VC-137C, airframeSAM26000, first VC-137C built]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airframeSAM26000 Context triple: [VC-137C, airframeSAM26000, first VC-137C built]
-
A.
airframe
Indicates that an entity is the structural framework or body of an aircraft associated with another entity (such as a specific model, component, or system).
-
B.
airframeDerivedFrom
Indicates that one airframe design is derived or developed from another pre-existing airframe design.
-
C.
airframer
Indicates a relationship where a company designs, manufactures, or assembles aircraft as its primary aerospace activity.
-
D.
airframeNumber
Indicates the unique identifying number assigned to a specific aircraft’s structural frame within a fleet or system.
-
E.
airframeConstruction
Indicates the method or structural approach used to build an aircraft’s main body and supporting framework.
- 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_69f76e0709408190bbe322bf1707ef6b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a34e80dc8190980d5b7b0b91341d |
completed | May 3, 2026, 7:34 p.m. |
Created at: May 3, 2026, 4:05 p.m.