Triple
T11327778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plaça de Sant Miquel |
E268265
|
entity |
| Predicate | streetNetworkContext |
P3374
|
FINISHED |
| Object | medieval street layout |
—
|
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: medieval street layout | Statement: [Plaça de Sant Miquel, streetNetworkContext, medieval street layout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetNetworkContext Context triple: [Plaça de Sant Miquel, streetNetworkContext, medieval street layout]
-
A.
streetNetwork
chosen
Indicates the layout and connectivity relationships among streets within a geographic area, including how roads intersect, link, and form a navigable network.
-
B.
streetSet
Indicates that a particular street belongs to, or is included within, a specified set or collection of streets.
-
C.
streetFunction
Indicates the functional role or primary use of a street within a transportation or urban context (e.g., residential, arterial, commercial access).
-
D.
streetPlanBy
Indicates that a street or road layout was designed, organized, or planned by a particular agent or authority.
-
E.
transportNetwork
Indicates a relationship where infrastructure or services enable the movement of people or goods between different locations.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9e330008190b75490efde01dc59 |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787afe5a48190b8af1a3e19529641 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.