Triple
T27537286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comoros archipelago volcanic chain |
E695129
|
entity |
| Predicate | nearbyMainlandCoast |
P169892
|
FINISHED |
| Object | Mozambique |
—
|
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: Mozambique | Statement: [Comoros archipelago volcanic chain, nearbyMainlandCoast, Mozambique]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyMainlandCoast Context triple: [Comoros archipelago volcanic chain, nearbyMainlandCoast, Mozambique]
-
A.
nearbyMainlandArea
chosen
Indicates that one area is located close to or adjacent to a mainland area.
-
B.
hasNearbyCoast
Indicates that one location is situated close to a coastline or seashore.
-
C.
nearestMainlandPoint
Indicates the relationship where a location is associated with the closest point on the mainland to that location.
-
D.
nearestCoastalTown
Indicates that one town is the closest coastal town geographically relative to a given reference location or town.
-
E.
connectsToCoastAt
Indicates that one entity has a direct physical or geographical connection or access to a coastline at the location of another entity.
- 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_69ef538608b081908b9f659bb09d5e0f |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: April 27, 2026, 1:29 p.m.