Triple
T12095540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunter Liggett |
E288061
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Hunter |
E238950
|
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: Hunter | Statement: [Hunter Liggett, givenName, Hunter]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hunter Context triple: [Hunter Liggett, givenName, Hunter]
-
A.
Hunter
Hunter is a seasoned, highly skilled assassin who serves as one of the central protagonists in the action thriller film "Killer Elite."
-
B.
Hunter
chosen
Hunter is a common English surname of occupational origin, historically referring to someone who hunted game for a living.
-
C.
Hunter
Hunter is a British heritage brand best known for its iconic rubber Wellington boots and outdoor footwear.
-
D.
Hunter
Hunter is a formidable and enigmatic bodyguard and warrior in Neil Gaiman's urban fantasy novel "Neverwhere," renowned for her unmatched prowess in tracking and combat within the hidden world of London Below.
-
E.
Hunter
Hunter is a ranged damage-dealing class in Hearthstone known for its aggressive playstyle, Beast synergies, and powerful direct-damage spells.
- 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_69d6ab4964708190850585628b287b0c |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d91552645c81909aff601ab3d3c0e6 |
completed | April 10, 2026, 3:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f5f6708f8881909c4f40a466bc0acf |
completed | May 2, 2026, 1:04 p.m. |
Created at: April 8, 2026, 9:48 p.m.