Triple
T2669926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eko Atlantic |
E55724
|
entity |
| Predicate | developedOn |
P41583
|
FINISHED |
| Object | reclaimed land |
—
|
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: reclaimed land | Statement: [Eko Atlantic, developedOn, reclaimed land]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedOn Context triple: [Eko Atlantic, developedOn, reclaimed land]
-
A.
developedWith
Indicates that something was created, built, or produced using a specified tool, technology, method, or collaborator.
-
B.
developedUnder
Indicates that something was created, produced, or brought into existence while being subject to the authority, guidance, or conditions imposed by a particular person, organization, regime, or framework.
-
C.
developedAs
Indicates that one entity was created, designed, or evolved specifically to function as or replace another entity.
-
D.
alsoDevelopedIn
Indicates that something was additionally developed in another context, location, or environment beyond the primary one already specified.
-
E.
developedPrimarilyIn
Indicates that something was mainly created, advanced, or brought into its primary form within a particular context, place, or domain, even if contributions occurred elsewhere.
- 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_69ab49e54de48190be708cd1cf8be073 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd98d32ac8190b8edd9421b706532 |
completed | March 7, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69abd8190ad481908f3e14ac84d0940a |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd8f98c348190a68064c565589459 |
completed | March 7, 2026, 7:51 a.m. |
Created at: March 6, 2026, 9:54 p.m.