Triple

T21224333
Position Surface form Disambiguated ID Type / Status
Subject ARP (Allocation and Retention Priority) E523051 entity
Predicate signalledOver P143268 FINISHED
Object NAS signaling 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: NAS signaling | Statement: [ARP (Allocation and Retention Priority), signalledOver, NAS signaling]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: signalledOver
Context triple: [ARP (Allocation and Retention Priority), signalledOver, NAS signaling]
  • A. signaled
    Indicates that one entity communicated a message, warning, or instruction to another through a deliberate signal or cue.
  • B. signalledQuantity
    Indicates that a specific quantity or amount has been conveyed or communicated, typically as part of a signal or message.
  • C. firstSignaledBy
    Indicates that a particular event, condition, or state was initially brought to attention or detected by a specified entity.
  • D. signalOfResult
    Indicates that one entity functions as a signal, marker, or indicator that a particular result, outcome, or state has occurred or will occur.
  • E. canBeSignaledBy
    Indicates that one entity is capable of being triggered, notified, or activated by another entity through some form of signaling.
  • 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_69e0b512ad94819087942b2ed925185f completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e734a9c9f88190817b574f916886e5 completed April 21, 2026, 8:26 a.m.
PD Predicate disambiguation batch_69e5f60e1a888190ba75e2e900270a4e completed April 20, 2026, 9:46 a.m.
PDg Predicate description generation batch_69e5f993240c8190847c0b08e65726c8 completed April 20, 2026, 10:01 a.m.
Created at: April 16, 2026, 3:44 p.m.