Triple
T9070726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tjalling C. Koopmans |
E217358
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Koopmans |
E217358
|
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: Koopmans | Statement: [Tjalling C. Koopmans, familyName, Koopmans]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Koopmans Context triple: [Tjalling C. Koopmans, familyName, Koopmans]
-
A.
Koopmans
chosen
Koopmans is a Dutch surname most notably associated with Nobel Prize–winning economist Tjalling C. Koopmans.
-
B.
Koops
Koops is a timid Koopa Troopa character and party member from the video game "Paper Mario: The Thousand-Year Door."
-
C.
Koppelman
Koppelman is a surname most notably associated with American screenwriter, director, and producer Brian Koppelman.
-
D.
Koos
Koos is the commonly used nickname of Koos de la Rey, a prominent Boer general and political figure from South African history.
-
E.
Koop
Koop is a surname most prominently associated with C. Everett Koop, the influential former Surgeon General of the United States.
- 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_69ca83d5a7f48190b16c1e59bd43ede0 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc955ec5c0819089bb42448edf391e |
completed | April 1, 2026, 3:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cffde470388190ae88a96654404410 |
completed | April 3, 2026, 5:50 p.m. |
Created at: March 30, 2026, 7:11 p.m.