Triple
T26323480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Hans-Adam II of Liechtenstein |
E662181
|
entity |
| Predicate | deFactoRegencyBegan |
P73392
|
FINISHED |
| Object | 15 August 2004 |
—
|
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: 15 August 2004 | Statement: [Prince Hans-Adam II of Liechtenstein, deFactoRegencyBegan, 15 August 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deFactoRegencyBegan Context triple: [Prince Hans-Adam II of Liechtenstein, deFactoRegencyBegan, 15 August 2004]
-
A.
regencyBegan
chosen
Indicates the point in time when a regency—rule exercised on behalf of another, typically a monarch—officially started.
-
B.
regencyBeganAfter
Indicates that the start of one regency occurred later in time than the start of another regency.
-
C.
periodOfRegency
Indicates the time span during which a regent exercised authority on behalf of the rightful ruler.
-
D.
regencyEnded
Indicates that a period during which one party governed on behalf of another (a regency) has come to an end.
-
E.
royalGovernmentStart
Indicates the point in time when a royal form of government is first established or begins to exercise authority.
- 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_69ee812e73048190aae587f1d51e5a06 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60f2e1fb48190aad56ac9683a267e |
completed | May 2, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:29 p.m.