Triple
T23987533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Line agreements |
E604978
|
entity |
| Predicate | legalStatusOfBorders |
P154149
|
FINISHED |
| Object | armistice lines not final political borders |
—
|
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: armistice lines not final political borders | Statement: [Green Line agreements, legalStatusOfBorders, armistice lines not final political borders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusOfBorders Context triple: [Green Line agreements, legalStatusOfBorders, armistice lines not final political borders]
-
A.
continentBorders
Indicates that one continent shares a land or maritime boundary directly with another continent.
-
B.
countryBorderRelation
Indicates that two countries share a common land or maritime boundary with each other.
-
C.
bordersInternationalBoundary
Indicates that one entity shares an international boundary line directly with another sovereign entity.
-
D.
countryBordering
Indicates that one country shares a land or maritime boundary directly with another country.
-
E.
bordersNation
Indicates that one nation shares a land or maritime boundary with another nation.
- 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_69e295463f7c8190b1c19dbd114641b9 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d38838f481909a52fccd392a92df |
completed | April 29, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f167dca3608190ace9d2eef56b2af6 |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 9:36 p.m.