Triple
T7815295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Pilger |
E180990
|
entity |
| Predicate | name |
P16
|
FINISHED |
| Object | Paul Pilger |
E180990
|
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: Paul Pilger | Statement: [Paul Pilger, name, Paul Pilger]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Paul Pilger Context triple: [Paul Pilger, name, Paul Pilger]
-
A.
Paul Pilger
chosen
Paul Pilger is an individual notable enough to be recognized as a bearer of the surname Pilger, though specific widely known public details about him are not readily available.
-
B.
Max Pilger
Max Pilger is a relatively obscure individual sharing the Pilger surname, with limited publicly available biographical or professional information.
-
C.
Walter Pilger
Walter Pilger is an individual notable enough to be recognized as a namesake or prominent bearer of the surname Pilger.
-
D.
Johann Pilger
Johann Pilger is an individual notable enough to be recorded as a bearer of the surname Pilger, though specific widely known biographical details about him are not readily available.
-
E.
Edward Pilger
Edward Pilger is an individual notable enough to be specifically cited as a bearer of the surname Pilger.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca828153f48190bdb27ac46f8e0745 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf96d1f088190a1d005ffb019afe9 |
completed | March 30, 2026, 10:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cb147d965881908003551710a1bbff |
completed | March 31, 2026, 12:25 a.m. |
Created at: March 30, 2026, 4:39 p.m.