Triple
T19985504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Care of Magical Creatures |
E493920
|
entity |
| Predicate | offeredToYear |
P138206
|
FINISHED |
| Object | third year |
—
|
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: third year | Statement: [Care of Magical Creatures, offeredToYear, third year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredToYear Context triple: [Care of Magical Creatures, offeredToYear, third year]
-
A.
applicationYear
Indicates the year in which an application was submitted or made.
-
B.
endorsedInYear
Indicates that one entity formally expressed support or approval for another entity during a specified calendar year.
-
C.
effectiveYear
Indicates the calendar year in which something (such as a rule, status, or agreement) becomes valid or takes effect.
-
D.
marketingYear
Indicates the specific 12‑month period used for planning, recording, or analyzing marketing or sales activities for a product or market.
-
E.
agreementYear
Indicates the calendar year in which an agreement between the related entities was made, signed, or came into effect.
- F. None of above. chosen
Provenance (4 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65d162b008190a18d325796d75d77 |
completed | April 20, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69e537fd311881908448f2aea8b4812e |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 11, 2026, 3:29 p.m.