Triple
T26257945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tombo Island |
E656761
|
entity |
| Predicate | cityDevelopedOn |
P160172
|
FINISHED |
| Object | Conakry |
—
|
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: Conakry | Statement: [Tombo Island, cityDevelopedOn, Conakry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityDevelopedOn Context triple: [Tombo Island, cityDevelopedOn, Conakry]
-
A.
cityDevelopedFrom
Indicates that a city originated, evolved, or was formed from a prior settlement, administrative unit, or urban entity.
-
B.
capitalDevelopedFrom
Indicates that a capital city originated, evolved, or was established based on a prior settlement, administrative center, or earlier form of capital.
-
C.
cityDevelopedBeside
Indicates that a city was developed in close proximity to and along the side of a particular geographic feature, settlement, or infrastructure.
-
D.
developedAsCityDueTo
Indicates that a settlement or area became a city specifically as a result of the influence, presence, or development of the referenced cause or factor.
-
E.
cityFoundedOn
Indicates that a city was established or officially founded on a specific date or point in time.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60dfcc97c8190903f2046c4861360 |
completed | May 2, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f5ffc6268c8190b63f6360ebadab73 |
completed | May 2, 2026, 1:44 p.m. |
Created at: April 26, 2026, 9:09 p.m.