Triple
T15355740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lego Harry Potter |
E367165
|
entity |
| Predicate | themeIntroduced |
P83876
|
FINISHED |
| Object | 2001 |
—
|
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: 2001 | Statement: [Lego Harry Potter, themeIntroduced, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: themeIntroduced Context triple: [Lego Harry Potter, themeIntroduced, 2001]
-
A.
introducedInTheme
chosen
Indicates that something (such as a concept, character, or element) is first presented or brought into use within a particular theme.
-
B.
theme
Indicates the entity that is the primary participant or content affected or characterized by an action, event, or state.
-
C.
introducedFeatureCategory
Indicates that an entity caused a particular feature category to be created, presented, or made available for the first time.
-
D.
introduced
Indicates that one entity caused another entity to become known, presented, or brought into use for the first time to a person, group, or context.
-
E.
themeFor
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
- 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_69d85a1483788190ad93c2748e8af34b |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e2c00648190ae2325e1ee58dcfd |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69deca991e5081908b0df3d1ee7d5338 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:18 a.m.