Triple
T334654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Labour Party (UK) |
E6697
|
entity |
| Predicate | firstEnteredGovernment |
P8145
|
FINISHED |
| Object | 1924 |
—
|
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: 1924 | Statement: [Labour Party (UK), firstEnteredGovernment, 1924]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstEnteredGovernment Context triple: [Labour Party (UK), firstEnteredGovernment, 1924]
-
A.
firstInOfficeTo
Indicates that one entity was the earliest or first to hold a particular office or position in relation to another entity or context.
-
B.
firstMinister
Indicates that one entity serves as the first minister (head of government or chief minister) of another entity, such as a country, region, or jurisdiction.
-
C.
ageAtFirstBecomingPrimeMinister
Indicates the age a person was when they first assumed the office of prime minister.
-
D.
cameToPowerIn
chosen
Indicates the time or context in which an entity assumed control, authority, or leadership over a group, organization, or territory.
-
E.
firstUsedInElection
Indicates that something (such as a method, technology, or rule) was used for the first time in a particular election.
- 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eac641708190b85fa21368e5de8e |
completed | Feb. 28, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69a2e94d99cc8190a112e4b630ec63c1 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.