Triple
T20155773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hogwarts Express |
E491561
|
entity |
| Predicate | returnFrequency |
P55256
|
FINISHED |
| Object | end of each Hogwarts term |
—
|
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: end of each Hogwarts term | Statement: [Hogwarts Express, returnFrequency, end of each Hogwarts term]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnFrequency Context triple: [Hogwarts Express, returnFrequency, end of each Hogwarts term]
-
A.
serviceFrequencyType
chosen
Indicates how often a service occurs or is scheduled within a given time period.
-
B.
serviceFrequencyContext
Indicates the contextual conditions or circumstances under which a service’s frequency is defined, applied, or interpreted.
-
C.
appointmentFrequency
Indicates how often appointments are scheduled or expected to occur within a given time period.
-
D.
redemptionFrequency
Indicates how often a redemption action or event occurs within a given time period.
-
E.
performedFrequency
Indicates how often an action or activity is carried out within a given time period.
- 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e667df7ac081908816d2d29e7c6513 |
completed | April 20, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69e54cfd924881909b55f3e4d3e7e070 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:34 p.m.