Triple
T15355622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lego Ninjago |
E367163
|
entity |
| Predicate | firstReleasedAsTheme |
P111447
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Lego Ninjago, firstReleasedAsTheme, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstReleasedAsTheme Context triple: [Lego Ninjago, firstReleasedAsTheme, 2011]
-
A.
firstReleasedAs
Indicates the original title or form under which an entity (such as a work, product, or version) was initially released before any later re-releases, renamings, or editions.
-
B.
firstUsedAsThemeInYear
chosen
Indicates the year in which something was first used as a theme.
-
C.
introducedInTheme
Indicates that something (such as a concept, character, or element) is first presented or brought into use within a particular theme.
-
D.
firstRelease
Indicates that one entity is the initial or earliest release (in time or sequence) of another entity, such as a product, work, or version.
-
E.
firstAiredAsThemeOn
Indicates that a work (such as a song or composition) was first broadcast or publicly introduced as the theme for another work (such as a show, series, or program).
- 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.