Triple
T1329737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTI |
E28613
|
entity |
| Predicate | denotesCountryIn |
P846
|
FINISHED |
| Object | ISO-based coding schemes |
—
|
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: ISO-based coding schemes | Statement: [HTI, denotesCountryIn, ISO-based coding schemes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denotesCountryIn Context triple: [HTI, denotesCountryIn, ISO-based coding schemes]
-
A.
countryRepresented
Indicates that one entity serves as the official representative (such as an athlete, diplomat, or delegate) of a specific country in a given context or event.
-
B.
hasCountry
chosen
Indicates that one entity possesses, is associated with, or is located within a specific country.
-
C.
meetsInCountry
Indicates that two or more entities have an in-person meeting that takes place within the specified country.
-
D.
alsoInCountry
Indicates that something located in one country is additionally located or present in another specified country.
-
E.
nationalityRepresented
Indicates the country or nation that an entity officially represents, typically in a professional, competitive, or diplomatic capacity.
- 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_69a498561a508190a3e1bc137c2b866a |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1c30c948190afc6342b3dcda948 |
completed | March 1, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69a4beef6a188190996f8775bdda8f6c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.