Triple
T30448355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | green flag of Libya |
E774641
|
entity |
| Predicate | containsBorder |
P198755
|
FINISHED |
| Object | no border |
—
|
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: no border | Statement: [green flag of Libya, containsBorder, no border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsBorder Context triple: [green flag of Libya, containsBorder, no border]
-
A.
hasBordersBy
Indicates that one entity shares a boundary or border with another entity.
-
B.
hasBorderThrough
Indicates that a border between two regions or entities passes through or along a specified intermediate area, feature, or object.
-
C.
hasBorderElement
Indicates that one entity includes or is associated with another entity that forms part of its boundary or edge.
-
D.
hadBorderType
Indicates that a boundary between two entities existed and specifies the nature or classification of that border (e.g., land, maritime, disputed).
-
E.
hasBorderCode
Indicates that there is an associated code or identifier specifying the type or status of a border between entities.
- 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_69f22493ef9c8190ae8c2afcb7f994c8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff0491409c8190be40f633a58da0b1 |
completed | May 9, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69ff040bb5cc81909534c7eee85d5e90 |
completed | May 9, 2026, 9:53 a.m. |
| PDg | Predicate description generation | batch_69ff04901ab081908b68563836fcdc99 |
completed | May 9, 2026, 9:55 a.m. |
Created at: April 29, 2026, 8:09 p.m.