Triple
T1025015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middelburg |
E22119
|
entity |
| Predicate | hasRebuiltHistoricCenter |
P23506
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Middelburg, hasRebuiltHistoricCenter, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRebuiltHistoricCenter Context triple: [Middelburg, hasRebuiltHistoricCenter, yes]
-
A.
hasHistoricCity
Indicates that an entity possesses, contains, or is associated with a city recognized for its historical significance.
-
B.
rebuiltAsPalace
Indicates that a structure or building was reconstructed or transformed into a palace.
-
C.
hasMajorHistoricalCentersIn
Indicates that an entity possesses significant, historically important centers or hubs located within a specified place or region.
-
D.
hasHistoricDistrict
Indicates that an entity possesses or contains a designated historic district within its boundaries or domain.
-
E.
capitalHistoric
Indicates that a location has served as a capital city at some point in history, even if it is not the current capital.
- 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_69a493d6e380819097b384986ffc315c |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7f4c66c8190b6098fb72c1465a3 |
completed | March 1, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69a4b72619cc8190932fdfa0c74dc055 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b7a0d0308190a00192aa9062bdaa |
completed | March 1, 2026, 10:03 p.m. |
Created at: March 1, 2026, 7:41 p.m.