Triple
T18300878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VectorEnv interface |
E438353
|
entity |
| Predicate | canBeBackedBy |
P131256
|
FINISHED |
| Object | process-based parallelism |
—
|
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: process-based parallelism | Statement: [VectorEnv interface, canBeBackedBy, process-based parallelism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeBackedBy Context triple: [VectorEnv interface, canBeBackedBy, process-based parallelism]
-
A.
backedFor
Indicates that one entity provides support, endorsement, or backing for another entity, often in a financial, political, or strategic context.
-
B.
canBePulledBackAlong
Indicates that a structure or object can be transferred or redefined along a given mapping or morphism so that it is compatible with that mapping.
-
C.
backingRequirement
Indicates that one entity must provide support, endorsement, or financial backing for another as a prerequisite or condition.
-
D.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
E.
canBeLinkedTo
Indicates that one entity has the potential or capability to be connected or associated with another entity.
- 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5017f63dc819083a675d570620f2f |
completed | April 19, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:35 a.m.