Triple
T12478574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet Air Force (limited VIP transport) |
E298240
|
entity |
| Predicate | aircraftOwnership |
P71026
|
FINISHED |
| Object | state-owned aircraft |
—
|
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: state-owned aircraft | Statement: [Soviet Air Force (limited VIP transport), aircraftOwnership, state-owned aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftOwnership Context triple: [Soviet Air Force (limited VIP transport), aircraftOwnership, state-owned aircraft]
-
A.
aircraftFlown
Indicates that an entity (typically a person or organization) operates or pilots a particular aircraft.
-
B.
aircraftOwnerOrLessee
chosen
Indicates that one entity owns or leases an aircraft associated with another entity.
-
C.
sharesAircraftWith
Indicates that two or more entities use, operate, or are associated with the same aircraft.
-
D.
aircraftInFleet
Indicates that a particular aircraft is included as a member of a specified fleet.
-
E.
poweredAircraftType
Indicates that one entity is a type or category of aircraft that is propelled by an onboard power source (e.g., engines), as opposed to being unpowered.
- 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_69d6ada377208190a36011199a4d8558 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e626dbc8190ac7dcdb542ba9b0c |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d3f701c81909dd0e00251ac8553 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:56 p.m.