Triple
T31626282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fred J. Koenekamp |
E807032
|
entity |
| Predicate | notableNominatedWork |
P25539
|
FINISHED |
| Object | Patton |
E288328
|
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: Patton | Statement: [Fred J. Koenekamp, notableNominatedWork, Patton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableNominatedWork Context triple: [Fred J. Koenekamp, notableNominatedWork, Patton]
-
A.
notableAwardWork
Indicates that a work is the specific creation (e.g., book, film, artwork) for which an award or honor was given.
-
B.
nominatedWork
chosen
Indicates that a particular work (such as a book, film, or artwork) has been put forward as a candidate for an award, honor, or recognition.
-
C.
notableWorkFeaturing
Indicates that a particular notable work (such as a book, film, or artwork) prominently includes, showcases, or is centered around a given entity.
-
D.
nominatedIn
Indicates that an entity has been formally put forward as a candidate for an award, position, or recognition within a specific event, context, or time period.
-
E.
notableWork
Indicates that one entity is a significant or well-known work (such as a book, artwork, or creation) produced by another entity.
- 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_69f348d7883c8190b6c13ab92b7ef076 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b945faf488190bc26e1f4d8276168 |
completed | June 12, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 10:43 p.m.