Triple
T23536605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rother Valley (UK Parliament constituency) |
E576715
|
entity |
| Predicate | LabourHeldContinuouslyFrom |
P22662
|
FINISHED |
| Object | 1918 |
—
|
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: 1918 | Statement: [Rother Valley (UK Parliament constituency), LabourHeldContinuouslyFrom, 1918]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: LabourHeldContinuouslyFrom Context triple: [Rother Valley (UK Parliament constituency), LabourHeldContinuouslyFrom, 1918]
-
A.
holdsWorkBy
Indicates that one entity possesses, contains, or displays a work that was created by another entity.
-
B.
continuesWorkBy
Indicates that one entity carries on, extends, or further develops the work previously initiated or performed by another entity.
-
C.
labourOf
Indicates that one entity is the work, effort, or labor performed or contributed by another entity.
-
D.
performedLabourAt
Indicates that an entity carried out work or labor activities at a specific place or organization.
-
E.
heldEvery
chosen
Indicates that an entity consistently possessed or maintained control of another entity throughout every instance or period within a specified range.
- 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_69e245f5a8848190a2ba42e271c6c31f |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ae1738bc81909a7b761ddbaa1883 |
completed | April 29, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:10 p.m.