Triple
T26131421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stewarts of Darnley |
E659256
|
entity |
| Predicate | crossBorderConnections |
P105151
|
FINISHED |
| Object | France |
—
|
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: France | Statement: [Stewarts of Darnley, crossBorderConnections, France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossBorderConnections Context triple: [Stewarts of Darnley, crossBorderConnections, France]
-
A.
crossBorderLinks
chosen
Indicates connections or interactions that extend across or link entities in different geographic or political jurisdictions.
-
B.
crossBorderFacilityConnectsTo
Indicates that a cross-border facility provides a direct physical or operational connection between two locations or infrastructures across a border.
-
C.
crossBorderNode
Indicates a connection or element that spans or links entities across a defined boundary or border.
-
D.
crossBorderRegion
Indicates a region that spans or intersects the boundary between two or more distinct territorial or jurisdictional areas.
-
E.
crossBorderPeople
Indicates the movement or presence of people across national or regional borders.
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 26, 2026, 8:15 p.m.