Triple

T24680868
Position Surface form Disambiguated ID Type / Status
Subject Metropolitan region Brabantse Stedenrij E611125 entity
Predicate isCommuterRegion P46264 FINISHED
Object true LITERAL FINISHED

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: true | Statement: [Metropolitan region Brabantse Stedenrij, isCommuterRegion, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isCommuterRegion
Context triple: [Metropolitan region Brabantse Stedenrij, isCommuterRegion, true]
  • A. isCommuterRegionFor
    Indicates that one region primarily serves as a residential base whose inhabitants regularly travel to another region for work or daily activities.
  • B. isCommuterHub
    Indicates that a location functions as a central node where many commuters start, end, or transfer during their regular travel.
  • C. hasCommuterPopulation chosen
    Indicates that a place has a significant number of people who regularly travel to or from it for work, study, or other routine activities.
  • D. isWithinMetroArea
    Indicates that one location lies inside the geographic boundaries of a specified metropolitan area.
  • E. isMetropolitanFor
    Indicates that one entity serves as the primary metropolitan center or urban hub for another entity (such as a region, area, or service).
  • 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_69e2c4d5c2dc8190ac857dea25ec6ce9 completed April 17, 2026, 11:40 p.m.
NER Named-entity recognition batch_69f41011d8048190be70329ba0bfb7c7 completed May 1, 2026, 2:29 a.m.
PD Predicate disambiguation batch_69f40ed9d47881909fcfc0d04e8d074a completed May 1, 2026, 2:24 a.m.
Created at: April 18, 2026, 3:08 a.m.