Triple
T18844750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCRPB |
E460886
|
entity |
| Predicate | regionTypePlanned |
P133153
|
FINISHED |
| Object | multi-state metropolitan region |
—
|
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: multi-state metropolitan region | Statement: [NCRPB, regionTypePlanned, multi-state metropolitan region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionTypePlanned Context triple: [NCRPB, regionTypePlanned, multi-state metropolitan region]
-
A.
regionType
Indicates the classification or category of a region, specifying what kind of region it is (e.g., administrative, geographic, or functional).
-
B.
plannedArea
Indicates that an area is designated or intended for a specific planned use or development.
-
C.
partOfPlanningRegion
Indicates that one entity is included within, or belongs to, a larger designated planning region.
-
D.
townPlannedWith
Indicates that a town was designed, organized, or laid out in coordination with a particular plan, entity, or planning effort.
-
E.
regionTypeOfPlace
Indicates that a place belongs to or is categorized under a specific type of geographic or administrative region.
- F. None of above. chosen
Provenance (4 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5b8ed944c81908592f0c34e5727a0 |
completed | April 20, 2026, 5:26 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:56 a.m.