Triple

T18008820
Position Surface form Disambiguated ID Type / Status
Subject Wireless Emergency Alerts E430822 entity
Predicate previousMessageLengthLimit P52424 FINISHED
Object 90 characters 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: 90 characters | Statement: [Wireless Emergency Alerts, previousMessageLengthLimit, 90 characters]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: previousMessageLengthLimit
Context triple: [Wireless Emergency Alerts, previousMessageLengthLimit, 90 characters]
  • A. hasCommunicationLimitation
    Indicates that an entity is subject to some restriction, constraint, or reduced capacity in its ability to communicate.
  • B. maximumBodyLength chosen
    Indicates that there is an upper limit on the allowable length or size of a body (e.g., content, message, or object) in this relationship or action.
  • C. fileNameLimit
    Indicates a constraint or maximum allowed length or format for a file’s name in a given context.
  • D. innerLimit
    Indicates a boundary or maximum value that applies within a specified internal or constrained context of something.
  • E. isLimitOf
    Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
  • 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_69d8b904530081908bf341d842464856 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4b51e13788190bebbbdd7340e0982 completed April 19, 2026, 10:57 a.m.
PD Predicate disambiguation batch_69e3f90039e4819080527f860dca042e completed April 18, 2026, 9:34 p.m.
Created at: April 10, 2026, 10:24 a.m.