Triple
T34103604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schraderbräu |
E874639
|
entity |
| Predicate | fictionalBrandType |
P194135
|
FINISHED |
| Object | beer brand |
—
|
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: beer brand | Statement: [Schraderbräu, fictionalBrandType, beer brand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalBrandType Context triple: [Schraderbräu, fictionalBrandType, beer brand]
-
A.
fictionalBrand
chosen
Indicates that one entity is a brand that exists only in fiction or narrative contexts, rather than in the real world.
-
B.
fictionalBusiness
Indicates that the referenced business entity exists only in fiction and does not operate as a real-world commercial organization.
-
C.
fictionalCorporation
Indicates that an entity is a corporation that exists only in fiction rather than in the real world.
-
D.
fictionalEntityType
Indicates that the subject is classified as a particular type or category of fictional entity within a narrative or imaginary context.
-
E.
fictionalType
Indicates that one entity is a fictional or imaginary type or category of the other 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_69f349a80d4481908527317d43f5c579 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69feb342994081909481ec8ec5d44928 |
completed | May 9, 2026, 4:08 a.m. |
| PD | Predicate disambiguation | batch_69feb046e4e48190b96649aa28529cc9 |
completed | May 9, 2026, 3:55 a.m. |
Created at: May 1, 2026, 1:53 a.m.