Triple
T25217383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fokker Scourge |
E631865
|
entity |
| Predicate | hasMainAircraft |
P66129
|
FINISHED |
| Object | Fokker Eindecker |
—
|
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: Fokker Eindecker | Statement: [Fokker Scourge, hasMainAircraft, Fokker Eindecker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainAircraft Context triple: [Fokker Scourge, hasMainAircraft, Fokker Eindecker]
-
A.
hasBasedAircraft
Indicates that an aircraft is regularly stationed or primarily based at a particular location or facility.
-
B.
hadBasedAircraftType
Indicates that a particular type of aircraft was stationed at or operated from a specific base or location.
-
C.
formerPrimaryAircraft
chosen
Indicates that an aircraft previously served as the main or primary aircraft for a given operator or entity, but no longer holds that status.
-
D.
usesCarrierAircraft
Indicates that one entity employs or operates aircraft that are designed to be launched from and recovered by an aircraft carrier.
-
E.
isProductionAircraft
Indicates that an aircraft is a standard, serially produced model rather than a prototype, experimental, or custom-built version.
- 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_69e75a8d1aa48190a4320acd3654762c |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 21, 2026, 12:59 p.m.