Triple
T7771397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johann Pilger |
E179078
|
entity |
| Predicate | name |
P16
|
FINISHED |
| Object | Johann Pilger |
E179078
|
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: Johann Pilger | Statement: [Johann Pilger, name, Johann Pilger]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Johann Pilger Context triple: [Johann Pilger, name, Johann Pilger]
-
A.
Johann Pilger
chosen
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.
-
B.
Paul Pilger
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.
-
C.
William Pilger
William Pilger is an individual notable enough to be recognized as a namesake or prominent bearer of the surname Pilger.
-
D.
Martin Pilger
Martin Pilger is an individual notable enough to be specifically cited as a bearer of the surname Pilger.
-
E.
Karl Pilger
Karl Pilger is an individual notable enough to be recognized as a namesake or distinguished 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_69c69f30602c819082ab52cd4af5c592 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c7045ebae88190a04c8f972795e615 |
completed | March 27, 2026, 10:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8c7ead45c8190847365d8549eefab |
completed | March 29, 2026, 6:34 a.m. |
Created at: March 27, 2026, 4:11 p.m.