Triple
T16219952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crysis 3 |
E393696
|
entity |
| Predicate | visualTechnology |
P122218
|
FINISHED |
| Object | real-time global illumination |
—
|
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: real-time global illumination | Statement: [Crysis 3, visualTechnology, real-time global illumination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visualTechnology Context triple: [Crysis 3, visualTechnology, real-time global illumination]
-
A.
viewTechnology
Indicates that an entity observes, inspects, or examines a particular technology.
-
B.
viewOnTechnology
Indicates how an entity perceives, evaluates, or holds opinions about technology and its role or impact.
-
C.
viewTechnologyIn
Indicates that a technology is being viewed, examined, or accessed within a particular context, location, or environment.
-
D.
visualMedium
Indicates that one entity serves as the visual medium or format through which another entity is presented, communicated, or experienced.
-
E.
visualCompanion
Indicates that one entity serves as a visual counterpart, partner, or accompanying element to another in a visual context.
- 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_69d87f204df88190a8f88923decf9835 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e227fabf708190a624c1ed8ce48b0a |
completed | April 17, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:03 a.m.