Triple
T13577890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poreč |
E324334
|
entity |
| Predicate | urbanPlanningOrigin |
P110134
|
FINISHED |
| Object | Roman period |
—
|
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: Roman period | Statement: [Poreč, urbanPlanningOrigin, Roman period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanPlanningOrigin Context triple: [Poreč, urbanPlanningOrigin, Roman period]
-
A.
originalUrbanPlanBy
Indicates that an urban plan was initially conceived or designed by a particular agent (such as a planner, architect, or organization).
-
B.
urbanPlanningFunction
Indicates a functional role or purpose that something serves within the planning, organization, or management of urban spaces and infrastructure.
-
C.
urbanPlanningTheme
Indicates a thematic relationship in which an entity is concerned with, addresses, or is categorized under topics related to urban planning.
-
D.
cityOfPlanning
Indicates the city where the planning or design activities for something (e.g., a project, event, or development) are carried out.
-
E.
urbanPlanInspiredBy
Indicates that an urban planning design, strategy, or project is conceptually derived from, modeled on, or significantly influenced by another plan, precedent, or source.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb02de1988190af2d473973ecd529 |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae161a0481909f9d3f40ca4e0ac5 |
completed | April 12, 2026, 2:37 p.m. |
| PDg | Predicate description generation | batch_69dbaf7fefa881908471f1400f813ccc |
completed | April 12, 2026, 2:43 p.m. |
Created at: April 9, 2026, 9:48 p.m.