Triple
T38338246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strathclyde Fire and Rescue |
E1038020
|
entity |
| Predicate | operatedInPart |
P50841
|
FINISHED |
| Object | western Scotland |
—
|
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: western Scotland | Statement: [Strathclyde Fire and Rescue, operatedInPart, western Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedInPart Context triple: [Strathclyde Fire and Rescue, operatedInPart, western Scotland]
-
A.
partlyOperatedBy
Indicates that an entity is operated or managed to some extent, but not entirely, by another entity.
-
B.
operatedPortionsOf
chosen
Indicates that an agent has performed operational control or management over specific parts or segments of a larger system, asset, or entity.
-
C.
operatedAmong
Indicates that an entity carried out operations or activities within, or in coordination with, a specified group, set, or collection of other entities.
-
D.
operatedAs
Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
-
E.
isPartOfOperation
Indicates that one entity functions as a component, phase, or element within a larger, overarching operation.
- 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_69f76e20d65c81909619ac0dd85c56f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a035b78140081908e451cb63d3c1c7c |
completed | May 12, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_6a035af3d8f48190bf1f3741d374404e |
completed | May 12, 2026, 4:53 p.m. |
Created at: May 3, 2026, 4:30 p.m.