Triple
T33382743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gabon–Republic of the Congo border |
E854827
|
entity |
| Predicate | languageOfBorderStates |
P77518
|
FINISHED |
| Object | French |
—
|
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: French | Statement: [Gabon–Republic of the Congo border, languageOfBorderStates, French]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfBorderStates Context triple: [Gabon–Republic of the Congo border, languageOfBorderStates, French]
-
A.
memberStatesShareBorderAlong
Indicates that two member states have a common boundary running along a specified geographic feature or segment.
-
B.
languageAlongBorder
chosen
Indicates that a particular language is spoken or prevalent along the border between two regions or entities.
-
C.
borderingCountryOfState
Indicates that one country shares a land or maritime boundary directly with the specified state.
-
D.
borderingStateOrTerritory
Indicates that one state or territory shares a common boundary with another state or territory.
-
E.
USStateBorderFor
Indicates that a U.S. state serves as a bordering state for the specified geographic or political entity.
- 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_69f3496d54048190a1cb91fdd7caa6ea |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0018cf6ebc8190aee6288788d0067e |
completed | May 10, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_6a001855e8588190a65840485473cf8b |
completed | May 10, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:35 a.m.