Triple
T17083092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tactical Air Force Wing 71 "Richthofen" |
E414523
|
entity |
| Predicate | hasNamesakeRank |
P27111
|
FINISHED |
| Object | Rittmeister |
—
|
LITERAL 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: Rittmeister | Statement: [Tactical Air Force Wing 71 "Richthofen", hasNamesakeRank, Rittmeister]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNamesakeRank Context triple: [Tactical Air Force Wing 71 "Richthofen", hasNamesakeRank, Rittmeister]
-
A.
hasFamousNamesake
Indicates that an entity shares its name with another well-known or notable entity.
-
B.
namedForRank
chosen
Indicates that something is named after a specific rank or title held by an entity.
-
C.
positionOfNamesake
Indicates that one entity occupies the role, rank, or spatial/organizational position associated with another entity for which it is named.
-
D.
hasNamesakeNotability
Indicates that one entity is notable or recognized specifically because it shares the same name as another entity.
-
E.
hasHonorificNamesake
Indicates that an entity is named in honor of another entity, serving as a namesake that recognizes or commemorates the other.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbe4d3908190b23ce3c2d3fe7d14 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.