Triple
T10367809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Human Traffic |
E244299
|
entity |
| Predicate | mainCharacter |
P1183
|
FINISHED |
| Object | Koop |
E860616
|
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: Koop | Statement: [Human Traffic, mainCharacter, Koop]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Koop Context triple: [Human Traffic, mainCharacter, Koop]
-
A.
Koop
Koop is a surname most prominently associated with C. Everett Koop, the influential former Surgeon General of the United States.
-
B.
Koop
chosen
Koop is a central character in the British cult film "Human Traffic," known for his role in the story’s depiction of youth and club culture.
-
C.
Koops
Koops is a timid Koopa Troopa character and party member from the video game "Paper Mario: The Thousand-Year Door."
-
D.
Coop
Coop is a central character in the work "Divisadero," around whom much of the story’s emotional and narrative focus revolves.
-
E.
Koopmans
Koopmans is a Dutch surname most notably associated with Nobel Prize–winning economist Tjalling C. Koopmans.
- 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e97106448190a075948e63184f47 |
completed | April 7, 2026, 11:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d7fb8e96e081908282bb0f82719abe |
completed | April 9, 2026, 7:18 p.m. |
Created at: April 6, 2026, noon