Triple

T32378553
Position Surface form Disambiguated ID Type / Status
Subject Hubs API E827350 entity
Predicate usesTransportAbstraction P185667 FINISHED
Object SignalR transport layer 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: SignalR transport layer | Statement: [Hubs API, usesTransportAbstraction, SignalR transport layer]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesTransportAbstraction
Context triple: [Hubs API, usesTransportAbstraction, SignalR transport layer]
  • A. usesTransport
    Indicates that an entity employs or relies on a particular mode or means of transportation to move from one place to another.
  • B. hasApproximateTransport
    Indicates that one entity is connected to another by a transport option whose route, timing, or characteristics are similar to, but not exactly the same as, a referenced or ideal transport connection.
  • C. isTransport
    Indicates that one entity serves as a means or method for conveying or carrying another entity from one place to another.
  • D. hasTransportFunction
    Indicates that an entity serves to move or carry something (such as people, goods, or signals) from one place or state to another.
  • E. assumesTransport
    Indicates that one entity takes responsibility for carrying or conveying another entity from one place to another.
  • 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_69f349177ddc8190ab0583f05597056b completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f7c33d59808190b647989a093f3488 completed May 3, 2026, 9:50 p.m.
PD Predicate disambiguation batch_69f7c1b6e7a881908deb96bedb2713f4 completed May 3, 2026, 9:44 p.m.
PDg Predicate description generation batch_69f7c29cf36481908e472d4dcb5573b9 completed May 3, 2026, 9:48 p.m.
Created at: May 1, 2026, 12:51 a.m.