Triple
T2740923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ndowe |
E60746
|
entity |
| Predicate | associatedWithCoast |
P17623
|
FINISHED |
| Object | Atlantic coast of Equatorial Guinea |
—
|
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: Atlantic coast of Equatorial Guinea | Statement: [Ndowe, associatedWithCoast, Atlantic coast of Equatorial Guinea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCoast Context triple: [Ndowe, associatedWithCoast, Atlantic coast of Equatorial Guinea]
-
A.
basedOnCoast
Indicates that something is situated along, adjacent to, or directly influenced by a coastline.
-
B.
extendsAlongCoastOf
Indicates that one entity stretches or runs parallel along the coastline of another entity.
-
C.
coastOff
Indicates that one entity is located just off the coast of another, typically in nearby offshore waters rather than directly on the shoreline.
-
D.
flowsAlongCoastOf
Indicates that something, typically a body of water or current, moves in a path that follows and runs adjacent to a coastline.
-
E.
hasNearbyCoast
chosen
Indicates that one location is situated close to a coastline or seashore.
- 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_69ab4b77febc819095603eb012cd141b |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb2f210881909126307cc92ebfef |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd829f1e88190aab1d54f87c69714 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.