Triple
T8867272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel 8085 |
E211049
|
entity |
| Predicate | hasProgramCounter |
P85087
|
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: [Intel 8085, hasProgramCounter, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProgramCounter Context triple: [Intel 8085, hasProgramCounter, true]
-
A.
hasProgramCode
Indicates that an entity is associated with a specific program identifier or code used to reference or classify it within a system.
-
B.
hasEngineProgram
Indicates that an entity is associated with or participates in a specific engine-related program.
-
C.
hasCalledProgram
Indicates that one program has invoked or executed another program.
-
D.
hasComponentProgram
Indicates that one program includes or is composed of another program as a component or sub-program.
-
E.
successorInProgram
Indicates that one element in a program directly follows another in the program’s execution or structural order.
- F. None of above. chosen
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_69ca838d3c7c8190a849566d5afd2b11 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6108530c819084559f4de669ce20 |
completed | April 1, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69cc5c279ea481908c71756f694b66bf |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cffe8ec819084c12770fe0578f2 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:51 p.m.