Triple

T1943888
Position Surface form Disambiguated ID Type / Status
Subject Address Supporting Organization E42017 entity
Predicate abbreviation P43 FINISHED
Object ASO E37216 NE 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: ASO | Statement: [Address Supporting Organization, abbreviation, ASO]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ASO
Context triple: [Address Supporting Organization, abbreviation, ASO]
  • A. ASO chosen
    ASO is one of ICANN’s supporting organizations responsible for overseeing global IP address policy development and coordination.
  • B. ASO
    ASO is a major French sports event management company best known for organizing the Tour de France and other prominent international competitions.
  • C. ASO Address Council
    The ASO Address Council is the elected body within ICANN’s Address Supporting Organization responsible for overseeing global Internet number resource policy development and advising the ICANN Board on related matters.
  • D. AS
    AS is the official vehicle registration code assigned to the Indian state of Assam.
  • E. AS
    AS is the two-letter IATA airline designator assigned to Alaska Airlines, used in flight numbers and ticketing.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69a8870e08fc8190a319cbf2600db15f completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abb2fe04688190aa8461ba090c93a0 completed March 7, 2026, 5:09 a.m.
NED1 Entity disambiguation (via context triple) batch_69adfbb9b594819096747b580ec18fee completed March 8, 2026, 10:44 p.m.
Created at: March 4, 2026, 7:36 p.m.