Triple
T7920949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Universal Render Pipeline |
E183941
|
entity |
| Predicate | isScriptable |
P30414
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Universal Render Pipeline, isScriptable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isScriptable Context triple: [Universal Render Pipeline, isScriptable, true]
-
A.
hasScriptTool
Indicates that an entity uses, is associated with, or is supported by a particular scripting tool or scripting environment.
-
B.
hasEditorScripting
chosen
Indicates that an entity provides or supports scripting capabilities specifically for editing or editor-related functionality.
-
C.
containsScript
Indicates that one entity includes or embeds the script of another entity within it.
-
D.
isScriptedInPart
Indicates that an entity is partially written, authored, or scripted in the specified language or scripting system, but not entirely.
-
E.
isExportable
Indicates that something can be legally and practically transferred or sent out from one jurisdiction, system, or context to another.
- 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_69ca828efbe48190bd48482650182e79 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a9360f881908ca2433d0623315b |
completed | March 31, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69cae9316e98819080be7bf1a6ff92f1 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:06 p.m.