Triple
T2384711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Graphics Group |
E46392
|
entity |
| Predicate | usedSoftware |
P17343
|
FINISHED |
| Object | RenderMan precursor technologies |
—
|
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: RenderMan precursor technologies | Statement: [Graphics Group, usedSoftware, RenderMan precursor technologies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedSoftware Context triple: [Graphics Group, usedSoftware, RenderMan precursor technologies]
-
A.
usesSoftware
Indicates that one entity employs or operates a particular software application or system to perform tasks or functions.
-
B.
programUsed
chosen
Indicates that a particular program, software, or application was employed or utilized in performing an action or achieving a result.
-
C.
commonSoftwareTools
Indicates that the related entities use or are associated with the same software tools.
-
D.
hardwareUsedBy
Indicates that a piece of hardware is utilized or operated by a particular entity (such as a person, system, or organization).
-
E.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
- 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_69a88a1554a48190a0180682bcf099be |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abc7bc87d0819090cd9d19d748bcc3 |
completed | March 7, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69abc59f73f08190924a36d7d475d8f4 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.