Triple
T28086381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Continental Region of Equatorial Guinea |
E709830
|
entity |
| Predicate | roadNetworkConnects |
P11435
|
FINISHED |
| Object | Ebebiyín |
—
|
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: Ebebiyín | Statement: [Continental Region of Equatorial Guinea, roadNetworkConnects, Ebebiyín]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadNetworkConnects Context triple: [Continental Region of Equatorial Guinea, roadNetworkConnects, Ebebiyín]
-
A.
roadConnectivityStatus
Indicates the current state of whether and how well two locations are connected by a road network.
-
B.
roadConnectionRegion
Indicates that a road provides a direct transportation connection between two regions.
-
C.
transportNetwork
Indicates a relationship where infrastructure or services enable the movement of people or goods between different locations.
-
D.
ropewayConnects
Indicates that a ropeway (such as a cable car or gondola system) provides a direct transportation connection between two locations.
-
E.
linkedByRoadTo
chosen
Indicates that two locations are directly connected to each other by a road suitable for travel.
- 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_69ef9b7037f0819095bb90eaccbcaf32 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 8:55 p.m.