Triple
T27681794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SRP Batcher |
E697927
|
entity |
| Predicate | enabledByDefaultIn |
P118343
|
FINISHED |
| Object | Universal Render Pipeline |
—
|
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: Universal Render Pipeline | Statement: [SRP Batcher, enabledByDefaultIn, Universal Render Pipeline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enabledByDefaultIn Context triple: [SRP Batcher, enabledByDefaultIn, Universal Render Pipeline]
-
A.
disabledByDefaultIn
Indicates that a feature, capability, or setting is turned off by default within the specified context or environment.
-
B.
enabledBy
Indicates that one entity functions as the cause, condition, or resource that makes it possible for another entity’s action, state, or capability to occur or be realized.
-
C.
includedByDefaultIn
chosen
Indicates that one entity is automatically present or enabled within another entity or context without requiring explicit selection or configuration.
-
D.
appliesByDefaultWhen
Indicates that one condition, rule, or behavior is automatically in effect whenever a specified situation or context occurs, without requiring explicit activation.
-
E.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 2:47 p.m.