Triple
T6492105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fritz Pfeffer |
E148064
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Pfeffer |
E463924
|
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: Pfeffer | Statement: [Fritz Pfeffer, familyName, Pfeffer]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pfeffer Context triple: [Fritz Pfeffer, familyName, Pfeffer]
-
A.
Pfeffer
chosen
Pfeffer is a German-origin surname borne by various notable individuals across fields such as academia, politics, and the arts.
-
B.
Onnion
Onnion is a small commune in the Haute-Savoie department of southeastern France, situated in the French Alps.
-
C.
Sabor
Sabor is the unicameral national legislature and representative body of the Republic of Croatia.
-
D.
Pfäfers
Pfäfers is a Swiss municipality in the canton of St. Gallen, known for its historic Benedictine monastery and scenic location in the Tamina valley.
-
E.
Pepusch
Pepusch is a surname most notably associated with Johann Christoph Pepusch, a German-born Baroque composer who worked extensively in London.
- 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_69c009088f3081909cd467b05919de30 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a9bf9208190b0957eda06ed3d65 |
completed | March 22, 2026, 10:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c653bf5c30819083e4e5484b2bd8cc |
completed | March 27, 2026, 9:54 a.m. |
Created at: March 22, 2026, 4:53 p.m.