Triple

T23312713
Position Surface form Disambiguated ID Type / Status
Subject Common Alerting Protocol E590625 entity
Predicate hasVersion P455 FINISHED
Object CAP 1.1 NE NERFINISHED

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: CAP 1.1 | Statement: [Common Alerting Protocol, hasVersion, CAP 1.1]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: CAP 1.1
Context triple: [Common Alerting Protocol, hasVersion, CAP 1.1]
  • A. CCAP
    CCAP is the stock ticker symbol for Corestate Capital, a European real estate investment and asset management company.
  • B. CAP
    CAP is the commonly used acronym for the Central Arizona Project, a major canal system that delivers Colorado River water to central and southern Arizona.
  • C. CAP chosen
    CAP (Common Alerting Protocol) is an international XML-based data format used for exchanging public warnings and emergency alerts across different systems and networks.
  • D. CAP
    CAP is the commonly used abbreviation for the Civil Air Patrol, the civilian auxiliary of the United States Air Force focused on emergency services, aerospace education, and cadet programs.
  • E. CAP
    CAP is a major Chilean mining and steel company that plays a key role in the country’s iron and steel production.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e25d1d32188190948eb76909d1dcc3 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1972ca70481909e2415c65964210a completed April 29, 2026, 5:29 a.m.
Created at: April 17, 2026, 5:06 p.m.