Triple
T13943954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Regent of the Netherlands |
E335330
|
entity |
| Predicate | hasRegencyType |
P112360
|
FINISHED |
| Object | temporary |
—
|
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: temporary | Statement: [Queen Regent of the Netherlands, hasRegencyType, temporary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegencyType Context triple: [Queen Regent of the Netherlands, hasRegencyType, temporary]
-
A.
hasRegency
Indicates that one entity exercises regency authority or governing power on behalf of another, typically during the latter’s minority, incapacity, or absence.
-
B.
passesThroughRegency
Indicates that something (such as a route, path, or boundary) traverses or goes through the area governed by a particular regency.
-
C.
hasEstateType
Indicates that an entity possesses or is associated with a particular category or type of estate.
-
D.
includesRegency
Indicates that one entity’s scope, period, or authority encompasses or contains a regency associated with another entity.
-
E.
hasMunicipalityType
Indicates that an administrative unit is classified as having a specific type or category of municipality (e.g., city, town, village).
- 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_69d81c6081b88190b53e317c3370c8fe |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e0f6f3c8190a64058b732b0ac52 |
completed | April 14, 2026, 12:07 p.m. |
| PD | Predicate disambiguation | batch_69de05a3ccf88190b45c742db483fa08 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239524688190a0f2408c239cfcaa |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:17 p.m.