Triple
T18937691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Tuns Brewery |
E463291
|
entity |
| Predicate | hasLicenceStatus |
P48284
|
FINISHED |
| Object | continuously licensed brewery |
—
|
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: continuously licensed brewery | Statement: [Three Tuns Brewery, hasLicenceStatus, continuously licensed brewery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLicenceStatus Context triple: [Three Tuns Brewery, hasLicenceStatus, continuously licensed brewery]
-
A.
hasLicense
Indicates that an entity possesses a valid authorization or permit, typically granted by an authority, to perform a specific activity or use something.
-
B.
licenseStatus
chosen
Indicates the current state or condition of a license in relation to its validity, permissions, or compliance.
-
C.
hasLicensing
Indicates that one entity holds or is granted licensing rights, permissions, or authorization in relation to another entity or resource.
-
D.
stateOfLicense
Indicates the jurisdiction or state that has issued or governs the relevant license.
-
E.
hasLegalStatus
Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
- 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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d3e8fdb48190ae70cb23c5bc2c97 |
completed | April 20, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 11:59 a.m.