Triple
T31024843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxcart program |
E790540
|
entity |
| Predicate | relatedAircraftFamily |
P83140
|
FINISHED |
| Object | Lockheed Blackbird family |
E223687
|
NE 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: Lockheed Blackbird family | Statement: [Oxcart program, relatedAircraftFamily, Lockheed Blackbird family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedAircraftFamily Context triple: [Oxcart program, relatedAircraftFamily, Lockheed Blackbird family]
-
A.
relatedAircraft
Indicates that there is an association or connection between two aircraft, such as operational, functional, or contextual relatedness.
-
B.
commonAircraftFamily
Indicates that two aircraft belong to the same aircraft family or series, sharing a common design lineage.
-
C.
aircraftFamilyIncludes
chosen
Indicates that a particular aircraft family encompasses or contains a given aircraft model or variant as a member of that family.
-
D.
notableAircraftFamily
Indicates that one entity is a well-known or historically significant family or series of aircraft associated with the other entity.
-
E.
relatesToAircraft
Indicates a general relationship or association between an entity and an aircraft, without specifying the exact nature of that connection.
- F. None of above.
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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a29389d7e748190bdcb1594f7dc5753 |
completed | June 10, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:58 p.m.