Triple
T26277674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Caledonian |
E660617
|
entity |
| Predicate | fleetIncludedAircraftType |
P98031
|
FINISHED |
| Object | McDonnell Douglas DC-10 |
—
|
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: McDonnell Douglas DC-10 | Statement: [British Caledonian, fleetIncludedAircraftType, McDonnell Douglas DC-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fleetIncludedAircraftType Context triple: [British Caledonian, fleetIncludedAircraftType, McDonnell Douglas DC-10]
-
A.
aircraftInFleet
chosen
Indicates that a particular aircraft is included as a member of a specified fleet.
-
B.
aircraftTypesUsedOn
Indicates the types or models of aircraft that are used on or assigned to a particular route, service, operation, or context.
-
C.
fleetType
Indicates the category or classification of a fleet to which an entity belongs or with which it is associated.
-
D.
fighterType
Indicates the specific combat or fighting style category that an entity belongs to.
-
E.
aircraftTypesCarried
Indicates that one entity (typically a vessel, facility, or platform) carries or is capable of carrying specific types of aircraft as part of its operations or configuration.
- 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_69ee812960d081909cff6085cc9fa3a6 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60e3641208190af80d23f7a692f3e |
completed | May 2, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 9:57 p.m.