Triple
T37232950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brayelles airfield |
E923189
|
entity |
| Predicate | usedByPilot |
P194639
|
FINISHED |
| Object | Manfred von Richthofen |
—
|
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: Manfred von Richthofen | Statement: [Brayelles airfield, usedByPilot, Manfred von Richthofen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByPilot Context triple: [Brayelles airfield, usedByPilot, Manfred von Richthofen]
-
A.
usedByPilotsOf
Indicates that something is utilized or operated by pilots belonging to a particular aircraft, organization, or group.
-
B.
pilotFor
Indicates that one entity serves as the pilot operating or navigating a vehicle, aircraft, or vessel on behalf of another entity (such as an organization, mission, or owner).
-
C.
pilotedIn
Indicates that an entity served as the pilot or operator of a vehicle, craft, or mission during a specific event or context.
-
D.
isPilot
Indicates that one entity serves as the pilot (operator in control of a vehicle or aircraft) for another entity.
-
E.
isPilotOf
Indicates that one entity serves as the pilot who operates or controls another entity, typically a vehicle or aircraft.
- F. None of above. chosen
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_69f76ea7f0008190b31b8e30f3d05a71 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
| PDg | Predicate description generation | batch_69fd7e35967081909f8bc8389d976ffd |
completed | May 8, 2026, 6:09 a.m. |
Created at: May 3, 2026, 4:15 p.m.