Triple
T38165998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brandenburg African Company |
E953144
|
entity |
| Predicate | operatedOnCoast |
P84004
|
FINISHED |
| Object | Gold Coast |
E34856
|
NE 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: Gold Coast | Statement: [Brandenburg African Company, operatedOnCoast, Gold Coast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedOnCoast Context triple: [Brandenburg African Company, operatedOnCoast, Gold Coast]
-
A.
basedOnCoast
Indicates that something is situated along, adjacent to, or directly influenced by a coastline.
-
B.
locatedOnCoastAt
chosen
Indicates that one entity is situated on the coastline at the specific location represented by another entity.
-
C.
isCoastalOn
Indicates that one entity is located along or directly borders the coastline of another entity (such as a body of water or sea).
-
D.
usedOnCoastOf
Indicates that something is utilized or applied in locations situated along the coast of a particular body of water.
-
E.
navigatedAlongCoastOf
Indicates that an entity traveled or steered a course following the coastline of another geographic entity.
- F. None of above.
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_69f76f0b93c48190a117319ab3a9f282 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a03544239d4819087b6c232d6804977 |
completed | May 12, 2026, 4:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41713279988190a2a60012656a4338 |
completed | June 28, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_6a0353d685688190b01df77fc2f62bf2 |
completed | May 12, 2026, 4:22 p.m. |
Created at: May 3, 2026, 4:21 p.m.