Triple
T32853563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pienza |
E840317
|
entity |
| Predicate | urbanPlanCommissionedBy |
P147302
|
FINISHED |
| Object | Pope Pius II |
—
|
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: Pope Pius II | Statement: [Pienza, urbanPlanCommissionedBy, Pope Pius II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanPlanCommissionedBy Context triple: [Pienza, urbanPlanCommissionedBy, Pope Pius II]
-
A.
urbanPlanBy
chosen
Indicates that an urban plan is created, designed, or authored by a specific agent or authority.
-
B.
urbanPlanApproved
Indicates that an official authority has reviewed and formally authorized a proposed urban development or land-use plan.
-
C.
urbanPlanningFunction
Indicates a functional role or purpose that something serves within the planning, organization, or management of urban spaces and infrastructure.
-
D.
cityOfPlanning
Indicates the city where the planning or design activities for something (e.g., a project, event, or development) are carried out.
-
E.
urbanPlanningForm
Indicates the specific type or structure of urban planning approach applied to a place or development.
- 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_69f349412c78819084459850e11d29f7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:17 a.m.