Triple
T29642166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gabon border near Ebebiyín |
E755889
|
entity |
| Predicate | borderDirectionRelativeToEbebiyín |
P195446
|
FINISHED |
| Object | south |
—
|
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: south | Statement: [Gabon border near Ebebiyín, borderDirectionRelativeToEbebiyín, south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderDirectionRelativeToEbebiyín Context triple: [Gabon border near Ebebiyín, borderDirectionRelativeToEbebiyín, south]
-
A.
borderDirectionFromCapital
Indicates the compass direction from a country's capital city to a specified border or neighboring entity.
-
B.
borderDirectionFromUS
Indicates the compass direction in which a country or region lies relative to the United States along their shared border.
-
C.
borderDefinedBy
Indicates that the boundary or limit of one entity is determined, shaped, or delineated by another entity.
-
D.
borderWithin
Indicates that one region’s border lies entirely inside the boundary of another region.
-
E.
countryBorderDirection
Indicates the cardinal or relative direction in which one country lies in relation to the border it shares with another country.
- 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_69f0ef89d2c88190a6d0d5116ccd7cc9 |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
| PDg | Predicate description generation | batch_69fdd2bda90881909aa229194d014ba7 |
completed | May 8, 2026, 12:10 p.m. |
Created at: April 28, 2026, 6:47 p.m.