Triple
T31884382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thermal Oxide Reprocessing Plant |
E813967
|
entity |
| Predicate | servesReactorsIn |
P198699
|
FINISHED |
| Object | United Kingdom |
—
|
NE NERFINISHED |
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: United Kingdom | Statement: [Thermal Oxide Reprocessing Plant, servesReactorsIn, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesReactorsIn Context triple: [Thermal Oxide Reprocessing Plant, servesReactorsIn, United Kingdom]
-
A.
servesClientsIn
Indicates that an entity provides services to clients located within a specified geographic area or jurisdiction.
-
B.
servesCircuit
Indicates that an entity provides legal representation or service in a specified judicial circuit.
-
C.
servedCircuit
Indicates that an entity (such as a legal case or document) has been formally delivered or notified to a specific judicial circuit or court jurisdiction.
-
D.
servedSystem
Indicates that one system has provided service, functionality, or resources to another system.
-
E.
sendsToServe
Indicates that one entity dispatches another entity to perform duties or fulfill a role at a specified place or for a particular purpose.
- 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69feff70fbec8190b1ff5f943f29613e |
completed | May 9, 2026, 9:33 a.m. |
| PD | Predicate disambiguation | batch_69fefbcd5b7881909cfe52b32f8a4301 |
completed | May 9, 2026, 9:18 a.m. |
| PDg | Predicate description generation | batch_69feff703fec8190ab7d0633e0cc5459 |
completed | May 9, 2026, 9:33 a.m. |
Created at: April 30, 2026, 11:57 p.m.