Triple

T17559354
Position Surface form Disambiguated ID Type / Status
Subject Global Enqueue Service E427659 entity
Predicate hasAbbreviation P43 FINISHED
Object GES 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: GES | Statement: [Global Enqueue Service, hasAbbreviation, GES]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: GES
Context triple: [Global Enqueue Service, hasAbbreviation, GES]
  • A. GES chosen
    GES is the stock ticker symbol for Guess?, Inc., an American clothing and accessories retailer known for its denim and fashion apparel.
  • B. GER
    GER is the official FIFA country code used to represent the Germany national football team in international competitions and records.
  • C. GER
    GER is the IATA airport code for Rafael Cabrera Mustelier Airport, which serves Nueva Gerona on Cuba’s Isla de la Juventud.
  • D. GS
    GS is the New York Stock Exchange ticker symbol for Goldman Sachs, a leading global investment banking, securities, and asset management firm.
  • E. GS
    GS is the vehicle registration code used on license plates for the town of Gospić in Croatia.
  • 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_69d889e0385081908a04b66f4dd4bd0d completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e4562573e48190a19f30fe915a5455 completed April 19, 2026, 4:12 a.m.
Created at: April 10, 2026, 5:50 a.m.