Triple
T8201384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mindstorms: Children, Computers, and Powerful Ideas |
E191581
|
entity |
| Predicate | titleInspired |
P21192
|
FINISHED |
| Object | Lego Mindstorms product line name |
—
|
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: Lego Mindstorms product line name | Statement: [Mindstorms: Children, Computers, and Powerful Ideas, titleInspired, Lego Mindstorms product line name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleInspired Context triple: [Mindstorms: Children, Computers, and Powerful Ideas, titleInspired, Lego Mindstorms product line name]
-
A.
inspiredTitle
chosen
Indicates that one title was created under the influence or inspiration of another title.
-
B.
title
Indicates that one entity serves as the formal name or designation of another entity.
-
C.
titleThrough
Indicates a relationship where one entity holds or is identified by a specific title by means of, or via the mediation of, another entity or context.
-
D.
titles
Indicates that one entity holds a formal title, designation, or name associated with another entity.
-
E.
aimedTitle
Indicates that one entity is the intended or targeted title or heading associated with another entity.
- 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_69ca82c7f3e08190857bf1fc63b2a10c |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb5df6e7548190846a1afd62ec6d0a |
completed | March 31, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69cb36aac86081909b83636e352e0ced |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:43 p.m.