Triple
T10521786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WritableStreamDefaultController |
E248190
|
entity |
| Predicate | propertyType(signal) |
P68889
|
FINISHED |
| Object | AbortSignal |
—
|
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: AbortSignal | Statement: [WritableStreamDefaultController, propertyType(signal), AbortSignal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propertyType(signal) Context triple: [WritableStreamDefaultController, propertyType(signal), AbortSignal]
-
A.
signalProperty
Indicates that one entity has a specific characteristic, attribute, or feature related to a signal.
-
B.
signalType
Indicates the specific kind or category of signal associated with or used by an entity or interaction.
-
C.
transportsSignalType
Indicates that one entity carries or conveys a particular type of signal from one point to another.
-
D.
searchesSignalType
Indicates that an entity actively looks for or queries a specific type or category of signal.
-
E.
propertyType_rtx
chosen
Indicates that one entity has a specific type or category of property in relation to 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509dec25881909bc748640f26a416 |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb94fa10819091f585bab4379c6f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:29 p.m.