Triple

T23143221
Position Surface form Disambiguated ID Type / Status
Subject South African National Route network E577516 entity
Predicate includesRoute P4374 FINISHED
Object N36
N36 is a designated national route within South Africa’s primary highway network, facilitating regional connectivity and transport.
E1574422 NE FINISHED

How this triple was built (4 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: N36 | Statement: [South African National Route network, includesRoute, N36]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: N36
Context triple: [South African National Route network, includesRoute, N36]
  • A. N366
    N366 is a regional road in the Netherlands that serves as a key connection route for traffic to and from the municipality of Pekela in the province of Groningen.
  • B. N363
    N363 is a regional road in the Netherlands that connects the village of Usquert with other nearby towns in the province of Groningen.
  • C. N367
    N367 is a regional road in the Netherlands that connects several towns in the province of Groningen, facilitating local and regional traffic.
  • D. N33
    N33 is a major Dutch regional highway in the northeastern Netherlands that connects several towns and motorways, facilitating north–south traffic in the region.
  • E. N35
    N35 is a major Dutch regional road connecting the city of Zwolle with Enschede in the province of Overijssel.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: N36
Triple: [South African National Route network, includesRoute, N36]
Generated description
N36 is a designated national route within South Africa’s primary highway network, facilitating regional connectivity and transport.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: N36
Target entity description: N36 is a designated national route within South Africa’s primary highway network, facilitating regional connectivity and transport.
  • A. N366
    N366 is a regional road in the Netherlands that serves as a key connection route for traffic to and from the municipality of Pekela in the province of Groningen.
  • B. N363
    N363 is a regional road in the Netherlands that connects the village of Usquert with other nearby towns in the province of Groningen.
  • C. N367
    N367 is a regional road in the Netherlands that connects several towns in the province of Groningen, facilitating local and regional traffic.
  • D. N33
    N33 is a major Dutch regional highway in the northeastern Netherlands that connects several towns and motorways, facilitating north–south traffic in the region.
  • E. N35
    N35 is a major Dutch regional road connecting the city of Zwolle with Enschede in the province of Overijssel.
  • F. None of above. chosen

Provenance (5 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_69e245f8e6248190ba3d58e068b4dccb completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18ecc3710819088ac5d72dad0459a completed April 29, 2026, 4:53 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0c3091b7b8819083d7fd257275bdd0 completed May 19, 2026, 9:42 a.m.
NEDg Description generation batch_6a0c317030c481908991f978ca15085e completed May 19, 2026, 9:46 a.m.
NED2 Entity disambiguation (via description) batch_6a0c322595308190b33c9e09fb26c2cc completed May 19, 2026, 9:49 a.m.
Created at: April 17, 2026, 4 p.m.