Triple
T34766541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nassau-Dietz |
E1002230
|
entity |
| Predicate | providedStadtholdersFor |
P82687
|
FINISHED |
| Object | Friesland |
—
|
NE NERFINISHED |
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: Friesland | Statement: [Nassau-Dietz, providedStadtholdersFor, Friesland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providedStadtholdersFor Context triple: [Nassau-Dietz, providedStadtholdersFor, Friesland]
-
A.
signatoryStadtholder
Indicates that an entity, serving as a stadtholder (provincial governor), is a formal signatory to a specific agreement, document, or treaty.
-
B.
officeHoldersTitleInDutch
Indicates that an office holder’s official title is given in the Dutch language.
-
C.
madeHereditaryStadtholder
Indicates that an individual was formally granted the position of stadtholder as a hereditary office, to be passed down through their family line.
-
D.
lastSovereignDuke
Indicates that the subject is the final individual to hold the title of sovereign duke over a given territory or domain.
-
E.
governingPeople
chosen
Indicates a relationship where one entity holds authority over and exercises control or administration of another group of people.
- 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_69f76db20dac8190b1e8d0ca4dc1d59f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fe6e492bf8819080b25221d13445ea |
completed | May 8, 2026, 11:14 p.m. |
| PD | Predicate disambiguation | batch_69fe6dd33a6881908fe9bbbc184cab51 |
completed | May 8, 2026, 11:12 p.m. |
Created at: May 3, 2026, 3:59 p.m.