Triple
T23460354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maxixe District |
E568954
|
entity |
| Predicate | locatedOppositeAcrossWaterFrom |
P64456
|
FINISHED |
| Object | Inhambane City |
—
|
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: Inhambane City | Statement: [Maxixe District, locatedOppositeAcrossWaterFrom, Inhambane City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOppositeAcrossWaterFrom Context triple: [Maxixe District, locatedOppositeAcrossWaterFrom, Inhambane City]
-
A.
locatedAcrossRiverFrom
Indicates that one entity is situated on the opposite side of a river relative to another entity.
-
B.
bodyOfWaterOnOtherSide
Indicates that one entity is located across a body of water from the other entity, with the water lying between them.
-
C.
nearestCityAcrossWater
Indicates that one city is the closest city to another city when considering only routes or separation across a body of water.
-
D.
acrossWaterFrom
chosen
Indicates that two entities are located on opposite sides of a body of water, separated by that water.
-
E.
oppositeShoreFrom
Indicates that two locations are situated on facing sides of the same body of water or shoreline, directly across from each other.
- 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_69e2458ebd808190b3298163132cfb0b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a69afba88190b1b1dd27d331309f |
completed | April 29, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:53 p.m.