Triple
T33843766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alo |
E867422
|
entity |
| Predicate | hasNeighboringTerritory |
P181353
|
FINISHED |
| Object | Uvea |
—
|
NE NERFINISHED |
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: Uvea | Statement: [Alo, hasNeighboringTerritory, Uvea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeighboringTerritory Context triple: [Alo, hasNeighboringTerritory, Uvea]
-
A.
hasNeighboringExclave
Indicates that one entity possesses an exclave that directly borders or is adjacent to an exclave of another entity.
-
B.
hasCountryBorderWith
Indicates that two countries share a common land or maritime boundary.
-
C.
hasBorderWithNonSovereignEntity
Indicates that one entity shares a land or maritime border with a political or territorial unit that is not fully sovereign.
-
D.
borderingCountryOfTerritory
Indicates that one country shares a land or maritime boundary with the specified territory.
-
E.
geographicallyBorders
chosen
Indicates that two geographic entities share a common boundary or border.
- 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_69f349937b648190a34ada70f6a2b534 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff956dc6548190979171d4b4068d47 |
completed | May 9, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69ff93dc39c481908a97a12c3ef7dfe7 |
completed | May 9, 2026, 8:06 p.m. |
Created at: May 1, 2026, 1:47 a.m.