Triple
T37962220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moy |
E947034
|
entity |
| Predicate | crossesCountyBorderNearby |
P13760
|
FINISHED |
| Object | County Armagh |
—
|
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: County Armagh | Statement: [Moy, crossesCountyBorderNearby, County Armagh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossesCountyBorderNearby Context triple: [Moy, crossesCountyBorderNearby, County Armagh]
-
A.
hasNearbyCountyBorder
Indicates that the borders of two counties are geographically close to each other, though not necessarily directly adjacent.
-
B.
crossesNear
Indicates that one entity passes across the path or area of another entity at a location that is close to, but not directly intersecting, the other entity.
-
C.
crossesBorderOf
chosen
Indicates that one entity passes from one side of the boundary of another entity (typically a region or area) to the other side, traversing its border.
-
D.
crossesRegion
Indicates that an entity moves through or passes across the spatial extent of a specified region.
-
E.
crossesStateBorders
Indicates that the referenced entity extends into or passes through more than one state’s territorial boundaries.
- 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_69f76ef7062c819091bfacb7e83aa1e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: May 3, 2026, 4:20 p.m.