Triple
T2271956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Four Corners Monument (Arizona corner) |
E50678
|
entity |
| Predicate | hasTypeOfBoundary |
P1972
|
FINISHED |
| Object | state boundary |
—
|
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: state boundary | Statement: [Four Corners Monument (Arizona corner), hasTypeOfBoundary, state boundary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfBoundary Context triple: [Four Corners Monument (Arizona corner), hasTypeOfBoundary, state boundary]
-
A.
hasBoundaryType
chosen
Indicates that one entity has a boundary characterized by a specific type or classification in relation to another entity or context.
-
B.
hasBoundaryFeature
Indicates that a boundary (such as an edge, border, or limit) of one entity is characterized, marked, or defined by a specific feature or element.
-
C.
hasBorderFacilityType
Indicates that a border facility possesses or is classified by a specific type or category of border-related infrastructure or service.
-
D.
hasBoundaryEvent
Indicates that an event occurs at or defines the boundary or limit of another entity or process.
-
E.
hasBorderTerminus
Indicates that one entity serves as the endpoint or terminal location of another entity’s border or boundary.
- 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_69a88b05910c8190a9a2b1ff230c85f9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc39c6ff0819081a07696f1c29990 |
completed | March 7, 2026, 6:20 a.m. |
| PD | Predicate disambiguation | batch_69abbdb7719081909143efa8f48df4e4 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.