Triple
T5253285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Broomsticks |
E118637
|
entity |
| Predicate | servesInFiction |
P795
|
FINISHED |
| Object | butterbeer |
—
|
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: butterbeer | Statement: [Three Broomsticks, servesInFiction, butterbeer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesInFiction Context triple: [Three Broomsticks, servesInFiction, butterbeer]
-
A.
hasFictionalWork
Indicates that one entity is the creator, owner, or source of a fictional work associated with another entity.
-
B.
residesInFictionalLocation
Indicates that an entity lives or is based in a location that is explicitly fictional or imaginary.
-
C.
appearsIn
chosen
Indicates that an entity is present, featured, or occurs within a particular context, work, or medium.
-
D.
hasFictionalUniverseElement
Indicates that one entity is a component, feature, or constituent part of the fictional universe represented by the other entity.
-
E.
hasFictionalRole
Indicates that an entity plays or is assigned a specific role within a fictional work or narrative.
- 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_69bd446978108190bb5f9c5c23d93f88 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b7cd7f4819098e591df07564a52 |
completed | March 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69bd77c30bac8190a883ca45da35d667 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:50 p.m.