Triple
T29867756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pixar production pipeline |
E758500
|
entity |
| Predicate | employsTool |
P91992
|
FINISHED |
| Object | RenderMan |
—
|
NE NERFINISHED |
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 | Statement: [Pixar production pipeline, employsTool, RenderMan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employsTool Context triple: [Pixar production pipeline, employsTool, RenderMan]
-
A.
toolIn
Indicates that one entity is a tool or instrument used in or associated with another entity or context.
-
B.
usesToolFor
chosen
Indicates that an agent employs a specific tool to carry out or facilitate a particular action or purpose.
-
C.
officialToolFor
Indicates that one entity is formally designated or authorized as the standard or primary tool to be used for another entity or purpose.
-
D.
toolUsed
Indicates that an action or task is performed using a particular tool as the means or instrument.
-
E.
toolDescribed
Indicates that one entity provides a description or explanation of a tool associated with 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 29, 2026, 5:52 p.m.