Triple
T34660595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hazzard County, Georgia |
E890095
|
entity |
| Predicate | hasFictionalRoad |
P90813
|
FINISHED |
| Object | Hazzard County roads |
—
|
LITERAL 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: Hazzard County roads | Statement: [Hazzard County, Georgia, hasFictionalRoad, Hazzard County roads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalRoad Context triple: [Hazzard County, Georgia, hasFictionalRoad, Hazzard County roads]
-
A.
hasRoads
Indicates that there exist constructed road connections linking the related entities.
-
B.
locatedOnFictionalRoute
chosen
Indicates that something is situated along or associated with a route that exists only within a fictional or imaginary setting.
-
C.
isNamedRoadIn
Indicates that a specific named road is located within or belongs to a particular geographic area or region.
-
D.
hasRoadway
Indicates that one location or area is connected to another by a road or roadway infrastructure.
-
E.
hasPermanentRoads
Indicates that an entity possesses roads that are constructed to be durable and remain in place over an extended period, rather than being temporary or seasonal.
- 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_69ff7ae5d088819089aa3b6360b6b749 |
completed | May 9, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69ff7a4df6488190bf60d675b36b1d6d |
completed | May 9, 2026, 6:17 p.m. |
Created at: May 1, 2026, 2:04 a.m.