Triple
T5057877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fredericia |
E113948
|
entity |
| Predicate | hasUrbanPlan |
P54635
|
FINISHED |
| Object | grid 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: grid street layout | Statement: [Fredericia, hasUrbanPlan, grid street layout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUrbanPlan Context triple: [Fredericia, hasUrbanPlan, grid street layout]
-
A.
mainUrbanPlan
chosen
Indicates the primary urban planning scheme or framework that governs the development and organization of a given area.
-
B.
partOfUrbanPlanBy
Indicates that something is included as a component or element within an urban plan created or overseen by a specified agent.
-
C.
hasUrbanFabric
Indicates that one entity possesses, contains, or is characterized by a particular pattern or structure of built-up urban development.
-
D.
hasPlannedCity
Indicates that an entity has a city that was deliberately designed and constructed according to a prearranged plan.
-
E.
hasUrbanFeature
Indicates that a place or area possesses a specific urban element or infrastructure feature (such as roads, parks, or buildings) as part of its built environment.
- 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_69bd443aa1f88190abb992d138f2cf42 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74523434819092b8b15992073b5b |
completed | March 20, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69bd715622b48190a3e8e49a5ef62b4a |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:38 p.m.