Triple
T33812540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QBasic |
E866575
|
entity |
| Predicate | notableExamplePrograms |
P32079
|
FINISHED |
| Object | Nibbles |
E1979451
|
NE 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: Nibbles | Statement: [QBasic, notableExamplePrograms, Nibbles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableExamplePrograms Context triple: [QBasic, notableExamplePrograms, Nibbles]
-
A.
notableProgramming
Indicates that an entity is notably associated with programming, such as being recognized for significant work, skill, or contributions in the field of programming.
-
B.
famousProgram
chosen
Indicates that a program is widely recognized or well-known, typically for its impact, quality, or popularity.
-
C.
notableProgrammingCategory
Indicates that an entity is recognized as belonging to a significant or distinguished category within the domain of programming.
-
D.
notableExampleBy
Indicates that something serves as a prominent or illustrative example provided or created by a particular entity.
-
E.
notableProgramsInclude
Indicates that the entity is known for or associated with offering or participating in the specified programs.
- F. None of above.
Provenance (4 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_69f349911a8c81908478662194b23d8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a366e992b708190829c9b81a46ce86b |
completed | June 20, 2026, 10:42 a.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:46 a.m.