Triple
T29711901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamina Fortress |
E751803
|
entity |
| Predicate | followsTownPlan |
P74423
|
FINISHED |
| Object | circular plan |
—
|
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: circular plan | Statement: [Hamina Fortress, followsTownPlan, circular plan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsTownPlan Context triple: [Hamina Fortress, followsTownPlan, circular plan]
-
A.
townPlannedWith
Indicates that a town was designed, organized, or laid out in coordination with a particular plan, entity, or planning effort.
-
B.
followsPlanType
chosen
Indicates that one entity adheres to, or is carried out according to, a specified type of plan.
-
C.
locatedInPlannedTown
Indicates that an entity is situated within the boundaries of a town that has been deliberately planned or designed rather than having developed organically.
-
D.
partOfUrbanPlanBy
Indicates that something is included as a component or element within an urban plan created or overseen by a specified agent.
-
E.
isPlannedTown
Indicates that a town has been deliberately designed and constructed according to a pre-established plan rather than developing organically over time.
- 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_69f0d62748848190b030d0a703629a7d |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: April 28, 2026, 7:31 p.m.