Triple
T37518542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | z-buffer algorithm |
E932699
|
entity |
| Predicate | typicallyImplementedIn |
P22535
|
FINISHED |
| Object | graphics hardware |
—
|
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: graphics hardware | Statement: [z-buffer algorithm, typicallyImplementedIn, graphics hardware]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyImplementedIn Context triple: [z-buffer algorithm, typicallyImplementedIn, graphics hardware]
-
A.
implementedFor
Indicates that one entity has been created, developed, or configured to operate on behalf of, or to fulfill the needs or requirements of, another entity.
-
B.
currentlyImplementedBy
Indicates that a given specification, design, or feature is presently realized or supported by a particular implementation or system.
-
C.
areImplementedBy
Indicates that one entity serves as the concrete realization or execution of the specification, design, or interface defined by another entity.
-
D.
implementedOn
chosen
Indicates that something (such as a feature, standard, or specification) is realized, executed, or put into effect within or on a particular platform, system, or environment.
-
E.
commonlyImplementedBy
Indicates that the referenced item (e.g., a standard, interface, or pattern) is frequently realized or put into practice by the associated implementing entities.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.