Triple
T27706077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UP |
E698562
|
entity |
| Predicate | dominantPeriodInGovernment |
P4210
|
FINISHED |
| Object | 1934–1948 |
—
|
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: 1934–1948 | Statement: [UP, dominantPeriodInGovernment, 1934–1948]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantPeriodInGovernment Context triple: [UP, dominantPeriodInGovernment, 1934–1948]
-
A.
dominantInStatePoliticsUntil
Indicates that an entity maintained a leading or controlling role in a state’s political affairs up to a specified point in time.
-
B.
periodOfKeyPoliticalRole
Indicates the time span during which an entity held a particular key political role or office.
-
C.
formedGovernmentTerm
Indicates that an entity established or initiated a specific term or period of governance for a government.
-
D.
periodOfRule
chosen
Indicates the span of time during which an entity exercised authority, control, or governance over something.
-
E.
governmentInPower
Indicates that a particular government currently holds official authority and is exercising ruling power over a state or region.
- 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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 27, 2026, 2:59 p.m.