Triple
T11483045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gildersome |
E272203
|
entity |
| Predicate | hasCountryCode |
P189
|
FINISHED |
| Object | GB |
E156042
|
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: GB | Statement: [Gildersome, hasCountryCode, GB]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GB Context triple: [Gildersome, hasCountryCode, GB]
-
A.
GB
chosen
GB is the ISO 3166-1 alpha-2 country code for the United Kingdom of Great Britain and Northern Ireland.
-
B.
GB
GB is a major generative grammar framework in linguistics developed by Noam Chomsky that explains how sentences are structured in the human mind.
-
C.
GB
GB is the common abbreviation for Gençlerbirliği S.K., a professional football club based in Ankara, Turkey.
-
D.
GB
GB is the regional code for Gilgit-Baltistan, a mountainous administrative territory in northern Pakistan known for its high peaks and strategic location.
-
E.
GA
GA is the commonly used abbreviation for General Atomics, an American energy and defense corporation known for its work in nuclear technology and unmanned aerial vehicles.
- 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_69d6aae1b09881909ce2ded3fa0c14fa |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d85a1d86b88190b180f6b0d0a27029 |
completed | April 10, 2026, 2:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e604410fbc819098b101c029b63525 |
completed | April 20, 2026, 10:47 a.m. |
Created at: April 8, 2026, 9:36 p.m.