Triple
T32353568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HDY |
E826667
|
entity |
| Predicate | hasCountryCodeContext |
P32679
|
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: [HDY, hasCountryCodeContext, GB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCountryCodeContext Context triple: [HDY, hasCountryCodeContext, GB]
-
A.
hasCountryContext
Indicates that something is associated with, interpreted within, or relevant to a specific country or national context.
-
B.
hasPrimaryCountryCode
Indicates that an entity is associated with its main or officially designated country code.
-
C.
isCountryCode
Indicates that one entity is a valid country code designating the country represented by the other entity.
-
D.
hasCodeContext
Indicates that an entity is associated with or occurs within a particular programming or code-related context.
-
E.
ISOCodeContext
chosen
Indicates the contextual framework or domain within which a particular ISO code is defined, interpreted, or applied.
- F. None of above.
Provenance (4 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_69f34915a2588190bb3178f5ec2f48f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a33e8a2c4b8819080695604e87e6a2c |
completed | June 18, 2026, 12:46 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:49 a.m.