Triple
T33382744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gabon–Republic of the Congo border |
E854827
|
entity |
| Predicate | borderStateCapital |
P199465
|
FINISHED |
| Object | Libreville |
—
|
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: Libreville | Statement: [Gabon–Republic of the Congo border, borderStateCapital, Libreville]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderStateCapital Context triple: [Gabon–Republic of the Congo border, borderStateCapital, Libreville]
-
A.
accessStateCapital
Indicates that an entity has the ability or permission to reach, use, or interact with the capital city of a given state.
-
B.
governingStateCapital
Indicates that a state serves as the governing political authority over the specified capital city.
-
C.
countryCapitalJurisdiction
Indicates that a specified capital city holds official administrative or governmental authority over a specified country.
-
D.
hasBorderingStateCapital
Indicates that one state capital city is directly adjacent to or shares a border with another state capital city.
-
E.
territoryCapital
Indicates that one entity is the capital city or administrative center of a specified territory.
- 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_69f3496d54048190a1cb91fdd7caa6ea |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff3b32ee148190a3ba3b7600943fef |
completed | May 9, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69ff3a238af88190a2c2245e30299e48 |
completed | May 9, 2026, 1:44 p.m. |
| PDg | Predicate description generation | batch_69ff3b323a748190827165f1cb274141 |
completed | May 9, 2026, 1:48 p.m. |
Created at: May 1, 2026, 1:35 a.m.