Triple
T10521799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WritableStreamDefaultController |
E248190
|
entity |
| Predicate | queueManagedAs |
P22105
|
FINISHED |
| Object | sequence of write records |
—
|
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: sequence of write records | Statement: [WritableStreamDefaultController, queueManagedAs, sequence of write records]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: queueManagedAs Context triple: [WritableStreamDefaultController, queueManagedAs, sequence of write records]
-
A.
queueType
chosen
Indicates the classification or category of a queue that specifies how items in it are organized, prioritized, or processed.
-
B.
queueTypical
Indicates that an entity is in or follows a standard or commonly expected queueing order or behavior relative to others.
-
C.
queueLocation
Indicates the place or position where an entity is arranged to wait in a queue or line.
-
D.
queueRelationship
Indicates a relationship where one entity is placed in an ordered waiting line relative to others, typically to await processing or access.
-
E.
queueEntranceName
Indicates the name assigned to the entrance of a queue.
- 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.