Triple
T35007491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kids' WB |
E1009850
|
entity |
| Predicate | programBlockType |
P2192
|
FINISHED |
| Object | network programming block |
—
|
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: network programming block | Statement: [Kids' WB, programBlockType, network programming block]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programBlockType Context triple: [Kids' WB, programBlockType, network programming block]
-
A.
programmingBlock
Indicates a relationship where one entity is a defined segment or unit of programming logic (such as a code block or script section) associated with or contained within another entity.
-
B.
programType
chosen
Indicates the category or kind of program to which an entity belongs or with which it is associated.
-
C.
programSequence
Indicates that one program or step occurs in a specific order directly before or after another within a defined sequence.
-
D.
programBasedOn
Indicates that one program is derived from, inspired by, or constructed using the content, structure, or principles of another program or source.
-
E.
program
Indicates that an entity creates, writes, or develops a computer program or software 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_69f76dcb716881909f75e4fd60ab2284 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7858aa5508190a07dde993b3356fc |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.