Triple
T10037079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Templeman |
E205196
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Templeman |
E205196
|
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: Templeman | Statement: [John Templeman, familyName, Templeman]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Templeman Context triple: [John Templeman, familyName, Templeman]
-
A.
Templeman
chosen
Templeman is an English-language surname borne by various notable individuals across fields such as music, sports, and public life.
-
B.
Shriever
Shriever is a surname, a variant spelling of "Shriver," borne by various individuals of English-speaking origin.
-
C.
No-Man
No-Man is a British art-pop and ambient rock band known for its atmospheric soundscapes and emotionally introspective songwriting.
-
D.
Devine
Devine is a surname of Irish origin borne by various notable individuals across fields such as sports, politics, and the arts.
-
E.
Dayman
Dayman is a fictional heroic persona from "It's Always Sunny in Philadelphia," featured in the show's satirical musical storyline.
- 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_69ca834f70e88190b2d74828b7767ec1 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcede428c8190ae115dc3425f9b0e |
completed | April 2, 2026, 2:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d3003098c0819093da30f98438680f |
completed | April 6, 2026, 12:37 a.m. |
Created at: March 30, 2026, 8:55 p.m.