Triple
T7716351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel 8008 |
E174894
|
entity |
| Predicate | stackImplementation |
P32204
|
FINISHED |
| Object | internal fixed-depth stack |
—
|
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: internal fixed-depth stack | Statement: [Intel 8008, stackImplementation, internal fixed-depth stack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stackImplementation Context triple: [Intel 8008, stackImplementation, internal fixed-depth stack]
-
A.
numberOfStacks
Indicates the count of distinct stacks associated with or contained within a given entity.
-
B.
stacking
Indicates that one entity is placed directly on top of another, forming a vertical arrangement or pile.
-
C.
isStackedWith
Indicates that one object is positioned directly on top of or beneath another object so that they form a vertical stack together.
-
D.
stackingConfiguration
Indicates how multiple entities are arranged or layered on top of each other in a specific order or configuration.
-
E.
usesDataStructure
chosen
Indicates that one entity employs or relies on a particular data structure in its operation or implementation.
- 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_69c6995c463c8190a14458036249d419 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c702ebb7448190ae8d47fe0cbb0907 |
completed | March 27, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69c701683dec8190be9861e592aa8ce0 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:04 p.m.