Triple
T10181594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LEGO Mindstorms RCX |
E236797
|
entity |
| Predicate | programmable |
P76293
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [LEGO Mindstorms RCX, programmable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programmable Context triple: [LEGO Mindstorms RCX, programmable, true]
-
A.
programmability
chosen
Indicates that an entity can be configured, controlled, or modified through programming or code to change its behavior or functions.
-
B.
programmatic
Indicates that one entity is created, controlled, or executed through code or automated software instructions rather than through manual or interactive means.
-
C.
programmedVia
Indicates that one entity is created, configured, or made to operate through the use of another entity as its programming method, tool, or medium.
-
D.
program
Indicates that an entity creates, writes, or develops a computer program or software application.
-
E.
madeProgram
Indicates that one entity created, developed, or authored a program (such as software or a coded application).
- 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_69ca84d7260c8190bfbec36762943f37 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cded32b91c8190b01ad37b2456080a |
completed | April 2, 2026, 4:14 a.m. |
| PD | Predicate disambiguation | batch_69cd7c79f21c8190a7f31b2eab80b8ba |
completed | April 1, 2026, 8:13 p.m. |
Created at: March 30, 2026, 9:12 p.m.