Triple
T38552661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roucourt airfield |
E925153
|
entity |
| Predicate | notablePilotPresent |
P43156
|
FINISHED |
| Object | Manfred von Richthofen |
E55113
|
NE 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: Manfred von Richthofen | Statement: [Roucourt airfield, notablePilotPresent, Manfred von Richthofen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePilotPresent Context triple: [Roucourt airfield, notablePilotPresent, Manfred von Richthofen]
-
A.
notablePilot
Indicates that an entity is a distinguished or noteworthy pilot associated with another entity (such as a vehicle, event, or organization).
-
B.
notablePilotOnRoute
Indicates that a particular pilot is notably associated with operating or having operated a specific route.
-
C.
hasPilot
Indicates that an entity is operated or controlled by a specific pilot.
-
D.
hasPilotAs
Indicates that one entity serves as the pilot or operator responsible for controlling another entity (typically a vehicle or aircraft).
-
E.
notablePresence
chosen
Indicates that an entity has a significant or prominent presence in relation to another entity, context, or domain.
- F. None of above.
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_69f76eaeb69c8190b367df9330d6f6af |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4223a4fdd0819081b660e67e48b4d0 |
completed | June 29, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.