Triple
T7156727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moordrecht |
E166829
|
entity |
| Predicate | partOfMunicipalitySince |
P75195
|
FINISHED |
| Object | 1 January 2010 |
—
|
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: 1 January 2010 | Statement: [Moordrecht, partOfMunicipalitySince, 1 January 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfMunicipalitySince Context triple: [Moordrecht, partOfMunicipalitySince, 1 January 2010]
-
A.
municipalityEstablished
Indicates that a municipality was officially created or founded at a specific point in time.
-
B.
unitaryAuthoritySince
Indicates the point in time from which an entity has held the status or role of a unitary authority.
-
C.
formerMunicipalityOf
Indicates that an entity was previously an independent municipality that has since been merged into or replaced by the referenced municipality.
-
D.
countySeatSince
Indicates that one place has served as the official county seat of a county starting from a specified point in time.
-
E.
isMunicipalHomeOf
Indicates that a municipality serves as the official home base or hosting location for a particular entity or organization.
- 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_69c68887a5cc8190bec0ea96227164f7 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e80dafdc8190b24863b83f084d12 |
completed | March 27, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69c6e1cd5c948190a9113b23f7308c21 |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e4a213508190a40aca39f9eee7d5 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:47 p.m.