Triple
T25132342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grampian Regional Council |
E629557
|
entity |
| Predicate | administeredFunction |
P160102
|
FINISHED |
| Object | roads |
—
|
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: roads | Statement: [Grampian Regional Council, administeredFunction, roads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administeredFunction Context triple: [Grampian Regional Council, administeredFunction, roads]
-
A.
administeredFunction
chosen
Indicates that an agent carries out, applies, or oversees the execution of a particular function or operation.
-
B.
administeredFor
Indicates that something (typically a treatment, medication, or intervention) is given or applied to an entity for a specific purpose, condition, or intended effect.
-
C.
administeredAs
Indicates that one entity is given or applied to another entity as a treatment, dose, or intervention.
-
D.
administeredWith
Indicates that two or more treatments, drugs, or interventions are given to a patient at the same time or as part of the same therapeutic regimen.
-
E.
administersFrom
Indicates that an action, service, or process is carried out or managed starting from a particular source, location, or authority.
- 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_69e2ff338250819096ff6c8892804389 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 18, 2026, 6:28 a.m.