Triple
T25071223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drenthe |
E627913
|
entity |
| Predicate | joinedKingdomOfTheNetherlands |
P157608
|
FINISHED |
| Object | 1815 |
—
|
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: 1815 | Statement: [Drenthe, joinedKingdomOfTheNetherlands, 1815]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: joinedKingdomOfTheNetherlands Context triple: [Drenthe, joinedKingdomOfTheNetherlands, 1815]
-
A.
joinedBelgiumFrom
Indicates that an entity became a member of or entered into Belgium from another specified entity or jurisdiction.
-
B.
dissolutionOfNetherlandsAntilles
Indicates the event or relationship in which the Netherlands Antilles ceased to exist as a political entity and its constituent territories underwent constitutional reorganization or change in status.
-
C.
joinedUnionOfUtrecht
Indicates that an entity became a member or signatory of the Union of Utrecht.
-
D.
succeededByInHolland
Indicates that one entity is directly followed or replaced by another entity in a succession specific to Holland.
-
E.
integratedIntoFrenchCrown
Indicates that a territory, institution, or authority was formally absorbed into and brought under the direct control of the French royal state.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f45d14c8a8819093a0cea7bcf56400 |
completed | May 1, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
| PDg | Predicate description generation | batch_69f448fe11f08190bdd53ca7ba2d51e4 |
completed | May 1, 2026, 6:32 a.m. |
Created at: April 18, 2026, 6:10 a.m.