Triple
T33252977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Zorner |
E851298
|
entity |
| Predicate | typeOfAces |
P85886
|
FINISHED |
| Object | Luftwaffe night fighter ace |
—
|
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: Luftwaffe night fighter ace | Statement: [Paul Zorner, typeOfAces, Luftwaffe night fighter ace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAces Context triple: [Paul Zorner, typeOfAces, Luftwaffe night fighter ace]
-
A.
typeOfAce
chosen
Indicates that one entity is classified as a specific type or category of ace (e.g., a particular kind of "ace" within a broader group).
-
B.
hasAces
Indicates that an entity possesses or is associated with one or more aces (typically in a card-related context).
-
C.
notableAce
Indicates that one entity is a particularly distinguished or outstanding example (an “ace”) within the domain or activity associated with the other entity.
-
D.
cardSetType
Indicates the classification relationship that specifies what type or category a given card set belongs to.
-
E.
highestScoringAce
Indicates that the subject is the ace (card, player, or entity) with the greatest score among all comparable aces in the given context.
- 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_69f34963135c819084e7f1d483421f00 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a00a846a8f881908b073ad13a5af6ca |
completed | May 10, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_6a00a7aae194819085e1a2fd406f7922 |
completed | May 10, 2026, 3:43 p.m. |
Created at: May 1, 2026, 1:31 a.m.