Triple
T16098715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shotz Brewery |
E390555
|
entity |
| Predicate | hasDepartmentFictional |
P78750
|
FINISHED |
| Object | bottling plant |
—
|
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: bottling plant | Statement: [Shotz Brewery, hasDepartmentFictional, bottling plant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDepartmentFictional Context triple: [Shotz Brewery, hasDepartmentFictional, bottling plant]
-
A.
hasDepartmentInFiction
chosen
Indicates that a fictional work includes or features a specific department as part of its setting or narrative.
-
B.
hasFictionalWork
Indicates that one entity is the creator, owner, or source of a fictional work associated with another entity.
-
C.
hasFictionalType
Indicates that an entity is associated with or classified under a particular type or category that is fictional rather than real.
-
D.
hasFictionalProductionCompany
Indicates that one entity is associated with or owns a production company that exists only within a fictional context.
-
E.
hasFictionalAuthor
Indicates that one entity is the fictional or in-universe author of a work attributed to them.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff6672848190922b5ebb90e18947 |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e182804208819087f35307cd6e4103 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:59 a.m.