Triple
T29060068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madawaska |
E735502
|
entity |
| Predicate | crossBorderRegionType |
P31352
|
FINISHED |
| Object | transnational cultural region |
—
|
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: transnational cultural region | Statement: [Madawaska, crossBorderRegionType, transnational cultural region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossBorderRegionType Context triple: [Madawaska, crossBorderRegionType, transnational cultural region]
-
A.
crossBorderRegion
chosen
Indicates a region that spans or intersects the boundary between two or more distinct territorial or jurisdictional areas.
-
B.
crossBorderSection
Indicates a section or segment that extends across or passes from one jurisdiction, region, or country into another.
-
C.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
-
D.
crossesRegion
Indicates that an entity moves through or passes across the spatial extent of a specified region.
-
E.
crossBorderNode
Indicates a connection or element that spans or links entities across a defined boundary or border.
- 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_69f077e85498819088b65186550da8cd |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 28, 2026, 10:14 a.m.