Triple
T31338198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poyle |
E799232
|
entity |
| Predicate | transferYearToSlough |
P196550
|
FINISHED |
| Object | 1995 |
—
|
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: 1995 | Statement: [Poyle, transferYearToSlough, 1995]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transferYearToSlough Context triple: [Poyle, transferYearToSlough, 1995]
-
A.
transferLine
Indicates a relationship where something is moved or conveyed from one point, medium, or entity to another along a defined path or channel.
-
B.
transferredToOxfordshire
Indicates that something or someone has been moved or reassigned to a location or authority in Oxfordshire.
-
C.
movedPremises
Indicates that an entity has changed its location or base of operations from one set of premises to another.
-
D.
transferPeriod
Indicates the time span or interval during which a transfer from one entity to another takes place.
-
E.
movedHeadquartersToLlantrisant
Indicates that an entity relocated its main headquarters to Llantrisant.
- F. None of above. chosen
Provenance (4 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_69f224e3f6ac8190a13488516abca7c9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe5c1a502081909d4024e514309c8e |
completed | May 8, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69fe5a9df21c819087153f5d0bcaa987 |
completed | May 8, 2026, 9:50 p.m. |
| PDg | Predicate description generation | batch_69fe5c196f4081908f150d4cd6c528fa |
completed | May 8, 2026, 9:56 p.m. |
Created at: April 29, 2026, 9:16 p.m.