Triple
T19083923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robby Krieger |
E467096
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Krieger |
—
|
NE NERFINISHED |
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: Krieger | Statement: [Robby Krieger, familyName, Krieger]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Krieger Context triple: [Robby Krieger, familyName, Krieger]
-
A.
Krieger
chosen
Krieger is a surname of German origin borne by various notable individuals across fields such as technology, music, and academia.
-
B.
Crayke
Crayke is a small village and civil parish in North Yorkshire, England, known for its historic hilltop setting and views over the surrounding countryside.
-
C.
Strucker
Strucker is a fictional antagonist, often depicted as a powerful and dangerous foe in comic book and related media storylines.
-
D.
Shriever
Shriever is a surname, a variant spelling of "Shriver," borne by various individuals of English-speaking origin.
-
E.
Crayne
Crayne is a surname and place name that serves as an alternative spelling of "Crain."
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e34600f88190bd96bcc2c5c08d14 |
completed | April 20, 2026, 8:26 a.m. |
Created at: April 10, 2026, 12:04 p.m.