Triple
T18460290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sovereign Prince of Liechtenstein |
E451013
|
entity |
| Predicate | regencySince |
P73392
|
FINISHED |
| Object | 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: 2004 | Statement: [Sovereign Prince of Liechtenstein, regencySince, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regencySince Context triple: [Sovereign Prince of Liechtenstein, regencySince, 2004]
-
A.
regencyBeganAfter
Indicates that the start of one regency occurred later in time than the start of another regency.
-
B.
regency
Indicates that one entity exercises ruling authority on behalf of another, typically when the latter is unable to govern directly (such as due to minority, absence, or incapacity).
-
C.
regencyBegan
chosen
Indicates the point in time when a regency—rule exercised on behalf of another, typically a monarch—officially started.
-
D.
includesRegency
Indicates that one entity’s scope, period, or authority encompasses or contains a regency associated with another entity.
-
E.
regencyStartApprox
Indicates that the beginning of a regency period is known only approximately rather than as an exact date.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e52a7e65bc8190a824bce5b322c3de |
completed | April 19, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69e469d05cf4819099baf1665a9cf18a |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:33 a.m.