Triple
T34491189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ovan |
E885469
|
entity |
| Predicate | hasNeighbouringCountryOfState |
P144172
|
FINISHED |
| Object | Republic of the Congo |
—
|
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: Republic of the Congo | Statement: [Ovan, hasNeighbouringCountryOfState, Republic of the Congo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeighbouringCountryOfState Context triple: [Ovan, hasNeighbouringCountryOfState, Republic of the Congo]
-
A.
borderingCountryOfState
chosen
Indicates that one country shares a land or maritime boundary directly with the specified state.
-
B.
hasNeighbouringState
Indicates that one state shares a common border or is directly adjacent geographically to another state.
-
C.
neighboringCountryPresence
Indicates that one country has a geographic presence (such as territory, bases, or influence) in or immediately adjacent to a neighboring country.
-
D.
hasCountryBorderWith
Indicates that two countries share a common land or maritime boundary.
-
E.
hasCapitalOnBorderingCountry
Indicates that the capital city of one country is located on the border it shares with 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_69f349cafcec8190997b45b3fdc16c27 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ffc89596d08190b97bd60b45c7f9c0 |
completed | May 9, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69ffc81ba5dc8190ae94d44e2284948f |
completed | May 9, 2026, 11:49 p.m. |
Created at: May 1, 2026, 2:01 a.m.