Triple
T29152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fife Council |
E581
|
entity |
| Predicate | isResponsibleFor |
P636
|
FINISHED |
| Object | local taxation in Fife |
—
|
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: local taxation in Fife | Statement: [Fife Council, isResponsibleFor, local taxation in Fife]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isResponsibleFor Context triple: [Fife Council, isResponsibleFor, local taxation in Fife]
-
A.
responsibleFor
chosen
Indicates that one entity has a duty, obligation, or role to manage, oversee, or be accountable for another entity or outcome.
-
B.
isSubjectTo
Indicates that one entity is governed, affected, or constrained by the authority, rules, conditions, or influence of another entity.
-
C.
isAbout
Indicates that one entity has as its subject, focus, or primary concern the content, topic, or theme represented by another entity.
-
D.
ownedBy
Indicates that one entity possesses legal or rightful ownership of another entity.
-
E.
recognizedFor
Indicates that one entity is acknowledged, credited, or honored for a particular achievement, quality, contribution, or work associated with another entity.
- 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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a2490019948190a89bb0910c60d462 |
completed | Feb. 28, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69a2486d40348190b2d21fc444f499a6 |
completed | Feb. 28, 2026, 1:44 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.