Triple
T25480718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N4 road (South Africa) |
E638563
|
entity |
| Predicate | partOfCorridorLinking |
P85888
|
FINISHED |
| Object | Gauteng |
—
|
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: Gauteng | Statement: [N4 road (South Africa), partOfCorridorLinking, Gauteng]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfCorridorLinking Context triple: [N4 road (South Africa), partOfCorridorLinking, Gauteng]
-
A.
linkedByCorridor
Indicates that two locations are directly connected to each other by a corridor.
-
B.
isPartOfCorridorSystem
chosen
Indicates that one entity forms a component or segment within a larger interconnected corridor system.
-
C.
passagewayConnection
Indicates a relationship where one passageway provides a direct route or link between two locations or spaces.
-
D.
inCorridor
Indicates that one entity is located within or inside a corridor relative to another spatial context or reference.
-
E.
hasCorridor
Indicates that one entity includes, is connected by, or provides access through a corridor to 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_69e75dbabeac8190bab30628f8b799d4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 21, 2026, 2:31 p.m.