Triple
T38214905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 278 in South Carolina |
E1010657
|
entity |
| Predicate | bridgeAccessTo |
P177955
|
FINISHED |
| Object | Hilton Head Island, South Carolina |
—
|
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: Hilton Head Island, South Carolina | Statement: [U.S. Route 278 in South Carolina, bridgeAccessTo, Hilton Head Island, South Carolina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgeAccessTo Context triple: [U.S. Route 278 in South Carolina, bridgeAccessTo, Hilton Head Island, South Carolina]
-
A.
bridgeAccessVia
chosen
Indicates that access to one entity is provided or routed through another entity acting as a bridge or intermediary.
-
B.
bridgeableWith
Indicates that two entities can be connected, linked, or made compatible through some bridging mechanism, process, or intermediary.
-
C.
bridgeUsed
Indicates that a bridge is utilized or traversed by an entity to cross between two locations or points.
-
D.
bridgeLocation
Indicates the specific place or area where a bridge is situated or spans.
-
E.
bridgeFeature
Indicates that one entity functions as a structural or functional feature of a bridge associated with another entity.
- 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_69f76dcdc7708190a5f1751d53f40ffe |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.