Triple
T24503674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greater Maputo area |
E618004
|
entity |
| Predicate | developsAround |
P136699
|
FINISHED |
| Object | city of Maputo |
—
|
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: city of Maputo | Statement: [Greater Maputo area, developsAround, city of Maputo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developsAround Context triple: [Greater Maputo area, developsAround, city of Maputo]
-
A.
developedAround
Indicates that one entity was created, designed, or evolved with the other entity as its central focus, basis, or surrounding context.
-
B.
developmentAround
chosen
Indicates that development or construction activity is occurring in the vicinity or surrounding area of a specified entity.
-
C.
developsWhen
Indicates that one condition, feature, or state comes into existence or forms as a result of another condition, feature, or state.
-
D.
developsDuring
Indicates that one process, condition, or characteristic comes into existence or forms over the course of a specified time period, phase, or event.
-
E.
developedWithin
Indicates that something was created, produced, or brought into existence inside a specified context, boundary, or time frame.
- 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_69e2d7f682108190a1a7ca5fd485ee8a |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:23 a.m.