Triple

T3769447
Position Surface form Disambiguated ID Type / Status
Subject European Currency Unit E82760 entity
Predicate symbol P129 FINISHED
Object ECU E4070 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: ECU | Statement: [European Currency Unit, symbol, ECU]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ECU
Context triple: [European Currency Unit, symbol, ECU]
  • A. ECU chosen
    ECU is the three-letter ISO 3166-1 alpha-3 country code that uniquely identifies Ecuador in international standards and data systems.
  • B. CAN
    CAN is the standard international abbreviation for the Canada men's national ice hockey team, one of the most successful and historically dominant teams in world ice hockey.
  • C. CAN
    CAN is a South American regional integration organization that promotes economic and social cooperation among its member countries, including Bolivia, Colombia, Ecuador, and Peru.
  • D. CAN
    CAN is the FIFA country code for Canada, the North American nation whose teams and players participate in international soccer competitions.
  • E. CAN
    CAN is the three-letter IATA airport code for Guangzhou Baiyun International Airport, a major air transport hub in southern China.
  • 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_69ad8b207b0081909d2b48843fbd8795 completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69adcc2f016c81909c2e3c85dbc3c259 completed March 8, 2026, 7:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4e5287908819084319b8dfa407635 completed March 14, 2026, 4:33 a.m.
Created at: March 8, 2026, 3:35 p.m.