Triple
T25305058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KR-48 |
E634457
|
entity |
| Predicate | hasCountryCodeElement |
P67388
|
FINISHED |
| Object | KR |
—
|
LITERAL 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: KR | Statement: [KR-48, hasCountryCodeElement, KR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCountryCodeElement Context triple: [KR-48, hasCountryCodeElement, KR]
-
A.
hasPrimaryCountryCode
Indicates that an entity is associated with its main or officially designated country code.
-
B.
hasCountryElement
chosen
Indicates that something includes, contains, or is composed of one or more country-related components or parts.
-
C.
isCountryCode
Indicates that one entity is a valid country code designating the country represented by the other entity.
-
D.
hasPrimaryExchangeCountryCode
Indicates the country code of the main securities exchange on which an entity is primarily listed or traded.
-
E.
hasPostalCountryCode
Indicates that an entity is associated with a specific country code used for postal addressing or mail routing.
- F. None of above.
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_69e75a972c6481909bc11710e8d30a6c |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 21, 2026, 1:25 p.m.