Triple
T4744518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arizona Sun Corridor |
E105326
|
entity |
| Predicate | planningConceptBy |
P56805
|
FINISHED |
| Object | Regional planning scholars |
—
|
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: Regional planning scholars | Statement: [Arizona Sun Corridor, planningConceptBy, Regional planning scholars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planningConceptBy Context triple: [Arizona Sun Corridor, planningConceptBy, Regional planning scholars]
-
A.
hasPlanningConcept
chosen
Indicates that an entity is associated with, defined by, or governed by a particular planning-related concept or framework.
-
B.
featuredConcept
Indicates that one concept is highlighted or given special prominence relative to others in a particular context.
-
C.
plannedWith
Indicates that an entity created or arranged a plan in collaboration or coordination with another entity.
-
D.
inspirationConcept
Indicates that one concept serves as a source of inspiration or creative influence for another concept.
-
E.
planningModelFor
Indicates that one entity serves as a planning model used to guide, simulate, or structure the planning activities related 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_69bd43ef87a48190a5bc3600711aa032 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64aa72c0819082ede0f531d75e65 |
completed | March 20, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69bd6221c3b881908604f35f8de6f16b |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:19 p.m.