Triple
T7114146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borgo Teresiano |
E165776
|
entity |
| Predicate | hasStreetPlanType |
P47409
|
FINISHED |
| Object | orthogonal grid |
—
|
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: orthogonal grid | Statement: [Borgo Teresiano, hasStreetPlanType, orthogonal grid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStreetPlanType Context triple: [Borgo Teresiano, hasStreetPlanType, orthogonal grid]
-
A.
hasStreetPlan
chosen
Indicates that an entity possesses or is associated with a specific layout or design plan for its streets.
-
B.
streetPlanBy
Indicates that a street or road layout was designed, organized, or planned by a particular agent or authority.
-
C.
hasFloorPlanShape
Indicates that an entity has a specific geometric or structural configuration defining the shape of its floor plan.
-
D.
isPlannedCity
Indicates that a city has been deliberately designed and constructed according to a pre-established urban plan rather than developing organically over time.
-
E.
hasStreetLevel
Indicates that something is located at, accessible from, or directly associated with the street level of a building or area.
- 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_69c6888227bc8190a1394679e3116f90 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5f0dab8819092103aefcaa1f9c2 |
completed | March 27, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c4f9788190830288d00cc37026 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:43 p.m.