Triple
T10521785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WritableStreamDefaultController |
E248190
|
entity |
| Predicate | propertyType(desiredSize) |
P93426
|
FINISHED |
| Object | number or null |
—
|
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: number or null | Statement: [WritableStreamDefaultController, propertyType(desiredSize), number or null]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propertyType(desiredSize) Context triple: [WritableStreamDefaultController, propertyType(desiredSize), number or null]
-
A.
propertyType_desiredSize
chosen
Indicates that a desired or preferred size is specified for a given property type.
-
B.
propertyType(size)
Indicates a relationship where an entity has a specific size as one of its properties.
-
C.
relativeSizeOnTethys
Indicates how the size of one entity compares to another specifically in the context of Tethys.
-
D.
propertyType_scaleResolutionDownBy
Indicates that one entity’s scale or resolution is reduced by a specified factor relative to another entity.
-
E.
hasRelativeSize
Indicates that one entity’s size is being compared to another entity’s size, expressing a relative rather than absolute magnitude.
- 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.