Triple
T26377273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel 4040 |
E660933
|
entity |
| Predicate | maximumStackDepth |
P1177
|
FINISHED |
| Object | 7 levels |
—
|
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: 7 levels | Statement: [Intel 4040, maximumStackDepth, 7 levels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumStackDepth Context triple: [Intel 4040, maximumStackDepth, 7 levels]
-
A.
maximumDepth
Indicates the greatest extent or deepest level reached by something within a given context or structure.
-
B.
maxStackSize
Indicates the maximum number of identical items or elements that can be grouped or stacked together as a single unit.
-
C.
hasMaximumDepth
chosen
Indicates that an entity possesses a greatest or limiting depth value beyond which it does not extend.
-
D.
maxDepthLocation
Indicates the location at which the maximum depth of something (e.g., an object, structure, or feature) is reached or measured.
-
E.
maximumProgramSize
Indicates the largest allowable or observed size of a program within a given context or system.
- 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 26, 2026, 11:02 p.m.