Triple
T3351485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middelharnis |
E70502
|
entity |
| Predicate | hasStreetPlan |
P47409
|
FINISHED |
| Object | historic village centre |
—
|
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: historic village centre | Statement: [Middelharnis, hasStreetPlan, historic village centre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStreetPlan Context triple: [Middelharnis, hasStreetPlan, historic village centre]
-
A.
streetPlanBy
Indicates that a street or road layout was designed, organized, or planned by a particular agent or authority.
-
B.
hasStreet
Indicates that an entity is located on, associated with, or identified by a particular street.
-
C.
hasStreetLayoutCenteredOn
Indicates that the spatial organization or pattern of streets in one place is arranged with a particular feature or location as its central focus or reference point.
-
D.
hasConnectingStreet
Indicates that two locations are linked by a street that directly connects them.
-
E.
hasPlannedCity
Indicates that an entity has a city that was deliberately designed and constructed according to a prearranged plan.
- 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_69ad85a4ef7c8190a29e2bbd6fa454e4 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb221a7d8819086cd0f826eca0fe8 |
completed | March 8, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69ada42fbe7c8190b9f185b5ab985f17 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada52716ec81908e89688a81039394 |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:12 p.m.