Triple
T4981463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sint Anthonis |
E111892
|
entity |
| Predicate | hasMunicipalHistoryUntil |
P52625
|
FINISHED |
| Object | 2021 |
—
|
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: 2021 | Statement: [Sint Anthonis, hasMunicipalHistoryUntil, 2021]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMunicipalHistoryUntil Context triple: [Sint Anthonis, hasMunicipalHistoryUntil, 2021]
-
A.
hasLocalGovernmentHistory
Indicates that an entity has a documented history or record of its local governmental structure, activities, or developments.
-
B.
hasMunicipalStatusUntil
chosen
Indicates that an entity possessed municipal status up to, but not beyond, a specified point in time.
-
C.
municipalityEstablished
Indicates that a municipality was officially created or founded at a specific point in time.
-
D.
hasMarketTownHistory
Indicates that an entity has a historical association with functioning as a market town or possessing recognized market-town status in the past.
-
E.
hasHistoricCity
Indicates that an entity possesses, contains, or is associated with a city recognized for its historical significance.
- 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_69bd441adc208190b70a033a0741d01e |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd74249a8c8190952680aee06a9286 |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd71492dec8190af4c27a3043b35cc |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:33 p.m.