Triple
T25408390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Jourimain, New Brunswick |
E636620
|
entity |
| Predicate | isLandfallOf |
P158485
|
FINISHED |
| Object | Confederation 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: Confederation Bridge | Statement: [Cape Jourimain, New Brunswick, isLandfallOf, Confederation Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLandfallOf Context triple: [Cape Jourimain, New Brunswick, isLandfallOf, Confederation Bridge]
-
A.
madeLandfallAt
Indicates that a storm or similar weather system has come ashore at a specific geographic location.
-
B.
madeLandfallOn
Indicates that a storm or similar weather system has come ashore and first reached land at a specific location or on a specific date.
-
C.
landfallLocation
Indicates the geographic location where a storm or similar weather system first makes landfall.
-
D.
hasIslandLanding
Indicates that an entity includes or provides a designated landing area or facility located on an island.
-
E.
landedNear
Indicates that one entity has come to rest on a surface or location in close proximity to another specified entity or reference point.
- 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_69e75db361d881908d8701c856da6413 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5b00c2a7481908f677dce983de140 |
completed | May 2, 2026, 8:04 a.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 1:52 p.m.