Triple
T18648249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brierfield Furnace |
E455859
|
entity |
| Predicate | hasFunctionStatus |
P100613
|
FINISHED |
| Object | no longer in operation |
—
|
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: no longer in operation | Statement: [Brierfield Furnace, hasFunctionStatus, no longer in operation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFunctionStatus Context triple: [Brierfield Furnace, hasFunctionStatus, no longer in operation]
-
A.
hasFunctionInWork
Indicates that an entity serves a specific role or performs a particular function within a given work (such as a creative, scholarly, or technical work).
-
B.
hasFunctionInPresent
Indicates that an entity currently performs, exhibits, or fulfills a specific function or role at the present time.
-
C.
hasFeatureStatus
chosen
Indicates that an entity possesses a particular feature along with its current state or condition.
-
D.
hasServiceFunction
Indicates that an entity performs, provides, or is responsible for a particular service-related function or role.
-
E.
hasHubFunction
Indicates that an entity serves as a central hub or coordinating point for certain activities, connections, or functions within a system.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5500f007c81908b1835569be913d7 |
completed | April 19, 2026, 9:58 p.m. |
| PD | Predicate disambiguation | batch_69e478d85864819093cbad5ed9b54878 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:47 a.m.