Triple
T31084347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Happy Hunting |
E792185
|
entity |
| Predicate | hasCharacter |
P2308
|
FINISHED |
| Object |
Liz Livingstone
Liz Livingstone is a fictional character from the work "Happy Hunting," likely serving as one of its central figures.
|
E1963521
|
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: Liz Livingstone | Statement: [Happy Hunting, hasCharacter, Liz Livingstone]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Liz Livingstone Triple: [Happy Hunting, hasCharacter, Liz Livingstone]
Generated description
Liz Livingstone is a fictional character from the work "Happy Hunting," likely serving as one of its central figures.
Provenance (5 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_69f224ce48348190bd0fc23f656ed683 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695fc607c8190a5735f3b4bded7db |
completed | May 3, 2026, 12:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b07524948819081a16841f5fb6ccb |
completed | June 11, 2026, 7:06 p.m. |
| NEDg | Description generation | batch_6a2b0a1a912c81908749b99c9701d441 |
completed | June 11, 2026, 7:18 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a2b0a86e768819098c8d52bbd3819cb |
completed | June 11, 2026, 7:20 p.m. |
Created at: April 29, 2026, 9:02 p.m.