Triple
T34660624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hazzard County, Georgia |
E890095
|
entity |
| Predicate | hasFictionalBridge |
P200433
|
FINISHED |
| Object | Hazzard County bridge |
—
|
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: Hazzard County bridge | Statement: [Hazzard County, Georgia, hasFictionalBridge, Hazzard County bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalBridge Context triple: [Hazzard County, Georgia, hasFictionalBridge, Hazzard County bridge]
-
A.
hasBridgeTo
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
-
B.
hasDrawbridge
Indicates that one entity possesses or is equipped with a drawbridge as part of its structure or features.
-
C.
hasNumberOfBridges
Indicates the quantitative relationship specifying how many bridges are associated with a given entity.
-
D.
hasFootbridge
Indicates that there exists a footbridge providing a pedestrian connection between the related entities.
-
E.
hasBridges
Indicates that one entity possesses, contains, or is characterized by one or more bridges connecting locations or components.
- F. None of above. chosen
Provenance (4 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_69ff8aff48988190a48a440de8238ef9 |
completed | May 9, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69ff8a780404819082f48ceb21e7fe11 |
completed | May 9, 2026, 7:26 p.m. |
| PDg | Predicate description generation | batch_69ff8afe9d5c8190bd5ae434fc2b550b |
completed | May 9, 2026, 7:29 p.m. |
Created at: May 1, 2026, 2:04 a.m.