Triple
T10328800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TransformStreamDefaultController |
E242826
|
entity |
| Predicate | method_terminate_parameters |
P93428
|
FINISHED |
| Object | none |
—
|
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: none | Statement: [TransformStreamDefaultController, method_terminate_parameters, none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: method_terminate_parameters Context triple: [TransformStreamDefaultController, method_terminate_parameters, none]
-
A.
connectionTerminationMethod
Indicates the method or process by which a connection between entities is ended or terminated.
-
B.
canTerminate
Indicates that one entity has the authority or ability to end or discontinue another entity, process, or relationship.
-
C.
terminatesOn
Indicates that one process, event, or state causes or marks the ending of another at a specific time or condition.
-
D.
terminationMechanism
Indicates the process or method by which an ongoing state, activity, or relationship is brought to an end.
-
E.
usesTerminator
Indicates that one entity employs or applies a specific terminator (such as an end marker, delimiter, or stopping mechanism) in relation to another entity or process.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7cfd54c8190b6f88598339536d1 |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f64a648190a79980d647898eb0 |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d7cada7881908beba55a1dc9ecb9 |
completed | April 7, 2026, 10:09 a.m. |
Created at: April 6, 2026, 11:52 a.m.