Triple
T21597945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Madrid (1795) |
E532951
|
entity |
| Predicate | establishesBoundaryLine |
P15022
|
FINISHED |
| Object | 31st parallel north |
—
|
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: 31st parallel north | Statement: [Treaty of Madrid (1795), establishesBoundaryLine, 31st parallel north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishesBoundaryLine Context triple: [Treaty of Madrid (1795), establishesBoundaryLine, 31st parallel north]
-
A.
setsBoundary
chosen
Indicates that one entity defines or forms the limiting edge or border of another entity.
-
B.
proposesBoundary
Indicates that one entity suggests or puts forward a specific boundary or limit to be considered or adopted in relation to another entity or context.
-
C.
fareBoundaryBetween
Indicates that there is a dividing line or zone where one fare region, zone, or pricing scheme ends and another begins.
-
D.
borderPoint
Indicates a point that lies on the boundary between two regions or entities.
-
E.
marksBoundaryIn
Indicates that one entity serves as a boundary or delimiter within, or for a specific region or structure of, another entity.
- 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_69e0c46364608190a337dc8720dc2a35 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eefae2fc908190b989f39e8cefffb2 |
completed | April 27, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69e632109d048190b4ac3f14fe48d1a0 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:32 p.m.