Triple
T17921773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hook Norton Brewery |
E448086
|
entity |
| Predicate | continuouslyOperatedSince |
P80913
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Hook Norton Brewery, continuouslyOperatedSince, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuouslyOperatedSince Context triple: [Hook Norton Brewery, continuouslyOperatedSince, 19th century]
-
A.
operatedSince
chosen
Indicates that an entity has been in operation continuously from a specified starting time or date.
-
B.
initiallyOperated
Indicates that an entity first began functioning, being used, or carrying out its intended operation at a specified initial time or under initial conditions.
-
C.
inUseSince
Indicates that an entity has been actively in use starting from a specified point in time.
-
D.
operatedAfter
Indicates that one operation or action occurred later in time than another specified operation or action.
-
E.
operatedAt
Indicates that an operation, procedure, or activity was performed at a specific location or facility.
- 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_69d8b9f6d394819082a6d69fd1e23d2f |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4a30a11748190be41361d108aee58 |
completed | April 19, 2026, 9:40 a.m. |
| PD | Predicate disambiguation | batch_69e3d8ec2f6881909d7f54b878cbed37 |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:20 a.m.