Triple
T20584536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Line |
E505749
|
entity |
| Predicate | notOfficialInternationalBorder |
P53620
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Blue Line, notOfficialInternationalBorder, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notOfficialInternationalBorder Context triple: [Blue Line, notOfficialInternationalBorder, true]
-
A.
notExactPoliticalBoundary
chosen
Indicates that the relationship involves a political boundary that is approximate, inferred, or otherwise not an exact or officially defined border between political entities.
-
B.
nearInternationalBoundary
Indicates that one entity is located close to an international boundary separating two or more countries.
-
C.
hasBorderWithNonSovereignEntity
Indicates that one entity shares a land or maritime border with a political or territorial unit that is not fully sovereign.
-
D.
bordersInternationalBoundary
Indicates that one entity shares an international boundary line directly with another sovereign entity.
-
E.
borderCountrySide
Indicates that one country shares a land border with the side or region of another country.
- 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_69e0b4b9669c8190b8e81fc72817d42c |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a975f098819083700593a9fa6cd0 |
completed | April 20, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69e59fffe1748190825e4eaa90340631 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:40 a.m.