Triple
T1153964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drenthe |
E23739
|
entity |
| Predicate | joinedAsProvince |
P25361
|
FINISHED |
| Object | 1796 |
—
|
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: 1796 | Statement: [Drenthe, joinedAsProvince, 1796]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: joinedAsProvince Context triple: [Drenthe, joinedAsProvince, 1796]
-
A.
servedProvince
Indicates that an entity has provided services or held jurisdictional authority over a specified province.
-
B.
hasSisterProvince
Indicates that two provinces are related to each other as sister provinces, typically through a formal partnership or cooperative relationship.
-
C.
isInProvince
Indicates that one entity (typically a place or city) is located within the administrative boundaries of a specified province.
-
D.
province
Indicates that one entity is an administrative subdivision or region (a province) governed by or belonging to another, typically larger, political or territorial entity.
-
E.
oneOfTwoProvincesOf
Indicates that an entity is one of exactly two provinces that together make up a specified larger region or political unit.
- 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_69a493f0d32c8190ac74bad3c87f2641 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc8e9cb481908a528a828b21d497 |
completed | March 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69a4bb50d19c81908a98dbbb04a8906f |
completed | March 1, 2026, 10:18 p.m. |
| PDg | Predicate description generation | batch_69a4bc47fce48190825d3a877251f789 |
completed | March 1, 2026, 10:23 p.m. |
Created at: March 1, 2026, 7:44 p.m.