Triple
T16261624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UK Parliament 1979–1983 |
E394767
|
entity |
| Predicate | eventDuringTerm |
P17853
|
FINISHED |
| Object | 1981 steel strike in the United Kingdom |
—
|
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: 1981 steel strike in the United Kingdom | Statement: [UK Parliament 1979–1983, eventDuringTerm, 1981 steel strike in the United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventDuringTerm Context triple: [UK Parliament 1979–1983, eventDuringTerm, 1981 steel strike in the United Kingdom]
-
A.
notableEventDuringTerm
chosen
Indicates that a significant or noteworthy event occurred during the time span of a particular term in office or period of service.
-
B.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
-
C.
regionDuringEvent
Indicates that a specified region is associated with or exists within the spatial scope of a particular event during its occurrence.
-
D.
officeHeldInPeriod
Indicates that an entity held a particular office or position during a specified time period.
-
E.
convenesDuring
Indicates that one entity formally gathers or brings together another entity or group during a specified time period or event.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c4a0b08190af3574f087205afc |
completed | April 17, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.