Triple
T29949100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATI Flipper |
E760720
|
entity |
| Predicate | maxTextureLayers |
P168286
|
FINISHED |
| Object | 8 |
—
|
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: 8 | Statement: [ATI Flipper, maxTextureLayers, 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxTextureLayers Context triple: [ATI Flipper, maxTextureLayers, 8]
-
A.
typicalLayerCount
Indicates the usual or standard number of layers associated with an entity.
-
B.
maximumResolution
Indicates the highest level of detail or fineness at which something (such as an image, display, or measurement) can be represented or processed.
-
C.
textureFeatures
Indicates that one entity possesses or is characterized by specific surface or material texture properties described by the other entity.
-
D.
usesTexture
Indicates that one entity employs or incorporates the texture of another entity in its appearance, design, or representation.
-
E.
textureRequirement
Indicates that one entity specifies or imposes a required texture property or characteristic that another entity must satisfy.
- 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_69f2246562b881909d57622f4086d43d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6780dd5d08190b1ef4e49405a5419 |
completed | May 2, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 6:25 p.m.