Triple
T34660599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hazzard County, Georgia |
E890095
|
entity |
| Predicate | hasFictionalOfficial |
P142216
|
FINISHED |
| Object | Boss Hogg |
—
|
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: Boss Hogg | Statement: [Hazzard County, Georgia, hasFictionalOfficial, Boss Hogg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalOfficial Context triple: [Hazzard County, Georgia, hasFictionalOfficial, Boss Hogg]
-
A.
hasFictionalLeader
Indicates that an entity is led or governed by a leader who is a fictional character rather than a real person.
-
B.
hasFictionalType
Indicates that an entity is associated with or classified under a particular type or category that is fictional rather than real.
-
C.
hasFictionalSpokesperson
chosen
Indicates that an entity is represented or promoted by a spokesperson who is a fictional or imaginary character.
-
D.
hasFictionalLeadCharacter
Indicates that a creative work features a particular fictional character as its main or leading protagonist.
-
E.
hasFictionalForm
Indicates that an entity has a counterpart or representation that exists within a fictional or imaginary context.
- F. None of above.
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_69f349d906bc8190b2efd9eff237d94b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff7bc112088190851501fb2a16103d |
completed | May 9, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69ff7b45507c81909753866ad733601a |
completed | May 9, 2026, 6:21 p.m. |
Created at: May 1, 2026, 2:04 a.m.