Triple
T11917541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nashwaaksis |
E283562
|
entity |
| Predicate | isConnectedByBridgeTo |
P36619
|
FINISHED |
| Object | Fredericton south side |
—
|
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: Fredericton south side | Statement: [Nashwaaksis, isConnectedByBridgeTo, Fredericton south side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isConnectedByBridgeTo Context triple: [Nashwaaksis, isConnectedByBridgeTo, Fredericton south side]
-
A.
hasBridgeTo
chosen
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
-
B.
hasBridgeAccess
Indicates that an entity is permitted to enter or use a specific bridge or bridge-controlled area.
-
C.
hasNumberOfBridges
Indicates the quantitative relationship specifying how many bridges are associated with a given entity.
-
D.
hasBridgeID
Indicates that a bridge is associated with a specific identifying code or number.
-
E.
hasBridges
Indicates that one entity possesses, contains, or is characterized by one or more bridges connecting locations or components.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e8deb14881909b65a1f159aec65f |
completed | April 10, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3632ac8190b13e53c2b5db7125 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.