Triple
T27403862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bleiswijk |
E691933
|
entity |
| Predicate | previouslyInstanceOf |
P23899
|
FINISHED |
| Object | independent municipality |
—
|
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: independent municipality | Statement: [Bleiswijk, previouslyInstanceOf, independent municipality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previouslyInstanceOf Context triple: [Bleiswijk, previouslyInstanceOf, independent municipality]
-
A.
previousInstanceOf
chosen
Indicates that one entity is an earlier occurrence or version of another entity in a sequence or history.
-
B.
laterInstanceOf
Indicates that one entity is a subsequent or later-occurring instance of the same type or pattern as another entity.
-
C.
possibleInstanceOf
Indicates that an entity may be an instance of a given class or type, but this classification is uncertain or not definitively established.
-
D.
namedAfterInstanceOf
Indicates that one entity is named after another entity that is an instance of a particular class or type.
-
E.
sonInstanceOf
Indicates that an entity is a specific instance or example of the general concept or class represented by "son."
- 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_69ef5205fc808190ad3efc5525b8e6d6 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: April 27, 2026, 12:30 p.m.