Triple
T35152984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trossö |
E1015042
|
entity |
| Predicate | inceptionAsTownPlan |
P41037
|
FINISHED |
| Object | late 17th century |
—
|
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: late 17th century | Statement: [Trossö, inceptionAsTownPlan, late 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inceptionAsTownPlan Context triple: [Trossö, inceptionAsTownPlan, late 17th century]
-
A.
hasStreetPlan
Indicates that an entity possesses or is associated with a specific layout or design plan for its streets.
-
B.
hasCityPlanShape
Indicates that an entity’s overall city layout or urban plan conforms to a particular geometric or structural shape.
-
C.
townPlannedWith
chosen
Indicates that a town was designed, organized, or laid out in coordination with a particular plan, entity, or planning effort.
-
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.
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_69f76ddb3a708190b521ba2970b17178 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.