Triple
T674549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of State of the Netherlands |
E13050
|
entity |
| Predicate | hasMonarchAsMember |
P4525
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Council of State of the Netherlands, hasMonarchAsMember, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMonarchAsMember Context triple: [Council of State of the Netherlands, hasMonarchAsMember, yes]
-
A.
monarchInvolved
chosen
Indicates that a monarch participates in, is associated with, or plays a role in a particular event, action, or situation.
-
B.
associatedWithMonarchyType
Indicates that an entity has a connection or relevance to a particular type or form of monarchy.
-
C.
monarchRole
Indicates that an entity holds or is assigned the role, office, or position of a monarch in relation to a state or domain.
-
D.
hasRoyalHouse
Indicates that an entity is associated with or belongs to a particular royal house or dynasty.
-
E.
monarchUntil
Indicates that an entity served as monarch over another entity up to, but not beyond, a specified end time or event.
- 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_69a4933d3bf88190972041cd8cf143b9 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a02537d08190942ee5fc8c50610a |
completed | March 1, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69a49d1bbd0c81909cfbec30bd17bde7 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.