Triple
T4551529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portugal and Spain |
E110173
|
entity |
| Predicate | haveSharedBorderSince |
P57960
|
FINISHED |
| Object | 12th century (approximate stabilization) |
—
|
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: 12th century (approximate stabilization) | Statement: [Portugal and Spain, haveSharedBorderSince, 12th century (approximate stabilization)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveSharedBorderSince Context triple: [Portugal and Spain, haveSharedBorderSince, 12th century (approximate stabilization)]
-
A.
hasBorderRelation
Indicates that one entity shares a boundary or border with another entity.
-
B.
hasBorderConnection
Indicates that two regions or entities share a common boundary or are directly connected along a border.
-
C.
guaranteedBorderBetween
Indicates a formally assured and recognized boundary relationship that definitively separates two regions or entities.
-
D.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
E.
hasBorderLocality
Indicates that one locality is situated along or adjacent to the border of another locality.
- F. None of above. chosen
Provenance (4 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_69bd4412524c8190be5bcc9ddee91848 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57f7b9748190af29d02fc77b02e0 |
completed | March 20, 2026, 2:21 p.m. |
| PD | Predicate disambiguation | batch_69bd5223423c81908317351b58cff5f5 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b4a9508190acdb888eef18f1ee |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:05 p.m.