Triple

T10328462
Position Surface form Disambiguated ID Type / Status
Subject ReadableStream E242819 entity
Predicate constructorAccepts P93392 FINISHED
Object underlyingSource object 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: underlyingSource object | Statement: [ReadableStream, constructorAccepts, underlyingSource object]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: constructorAccepts
Context triple: [ReadableStream, constructorAccepts, underlyingSource object]
  • A. canBeConstructedWith
    Indicates that one entity can be formed, built, or assembled using another entity as material, components, or means.
  • B. hasConstructor
    Indicates that an entity defines or is associated with a specific constructor used to create or initialize instances of it.
  • C. constructedAs
    Indicates that one entity is built, formed, or created in the manner, structure, or configuration specified by another entity.
  • D. hasConstructorParticipation
    Indicates that an entity participates in the creation or construction process of another entity.
  • E. constructedUnder
    Indicates that something was built, created, or assembled while subject to the authority, direction, or conditions imposed by a particular agent, rule, plan, or regime.
  • 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_69d4d7cf21e08190bf605daeea0d9dcf 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.