Triple
T18628113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BR-277 |
E455335
|
entity |
| Predicate | connectsInlandToCoast |
P108869
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [BR-277, connectsInlandToCoast, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsInlandToCoast Context triple: [BR-277, connectsInlandToCoast, true]
-
A.
connectsInlandCityToCoast
Indicates a relationship where a route, link, or infrastructure connects an inland city to a coastal area or city.
-
B.
connectsCoastToInland
Indicates a relationship where something (such as a route, structure, or feature) links a coastal area to an inland area.
-
C.
connectsCoastToBorder
Indicates a relationship where something (such as a route, feature, or boundary) links a coastal area directly to a national or regional border.
-
D.
connectsToCoastAt
Indicates that one entity has a direct physical or geographical connection or access to a coastline at the location of another entity.
-
E.
connectsInlandCommunitiesTo
chosen
Indicates a relationship in which something serves as a link or conduit between inland communities and another place, system, or network.
- 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_69d8d38cc7948190a55ea64e5638994e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54f063a1c819087e544c64f5cf80f |
completed | April 19, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:46 a.m.