Triple
T26841612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airspeed Oxford |
E675791
|
entity |
| Predicate | derivedCivilVariant |
P99225
|
FINISHED |
| Object | Airspeed Consul |
—
|
NE NERFINISHED |
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: Airspeed Consul | Statement: [Airspeed Oxford, derivedCivilVariant, Airspeed Consul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: derivedCivilVariant Context triple: [Airspeed Oxford, derivedCivilVariant, Airspeed Consul]
-
A.
developedFromCivilModel
chosen
Indicates that something was created or derived based on a pre-existing civil model.
-
B.
civilianVariant
Indicates that one entity is a civilian version or non-military counterpart of another entity.
-
C.
exportVariantOf
Indicates that one entity is an exported version or externally released form derived from another, original entity.
-
D.
customizedVariantOf
Indicates that one entity is a modified or tailored version derived from another, preserving a core basis while introducing specific customizations.
-
E.
governsVariant
Indicates a regulatory relationship where one entity controls, influences, or determines the behavior or state of a specific variant 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_69eee9b8d5e88190a07d3455c0fbb21f |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 27, 2026, 5:08 a.m.