Triple

T15220288
Position Surface form Disambiguated ID Type / Status
Subject ISO 3166-2:GS E363747 entity
Predicate countryCode P208 FINISHED
Object GS E73757 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: GS | Statement: [ISO 3166-2:GS, countryCode, GS]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: GS
Context triple: [ISO 3166-2:GS, countryCode, GS]
  • A. GS chosen
    GS is the two-letter ISO 3166 country code assigned to the British Overseas Territory of South Georgia and the South Sandwich Islands in the southern Atlantic Ocean.
  • B. GS
    GS is the vehicle registration code used on license plates for the district of Goslar in Lower Saxony, Germany.
  • C. GS
    GS is the New York Stock Exchange ticker symbol for Goldman Sachs, a leading global investment banking, securities, and asset management firm.
  • D. GS
    GS is the vehicle registration code used on license plates for the town of Gospić in Croatia.
  • E. GS
    GS is the common abbreviation for United Global Services, United Airlines’ invitation-only elite frequent flyer status for its most valuable customers.
  • 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_69d85a0ce24c81909c4d3b6475548c95 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e007709d3881908384f0fe1e0218d0 completed April 15, 2026, 9:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69fed346faf48190924697a04f74f22a completed May 9, 2026, 6:25 a.m.
Created at: April 10, 2026, 3:11 a.m.