Triple
T18277382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AN |
E437772
|
entity |
| Predicate | codeStatusInISO3166 |
P78768
|
FINISHED |
| Object | deleted entry |
—
|
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: deleted entry | Statement: [AN, codeStatusInISO3166, deleted entry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeStatusInISO3166 Context triple: [AN, codeStatusInISO3166, deleted entry]
-
A.
ISO3166Status
chosen
Indicates the classification or current standing of an entity under the ISO 3166 country code standard (e.g., official, reserved, or deleted status).
-
B.
countrySpecificStatus
Indicates a status or condition that is defined or applied specifically in the context of a particular country.
-
C.
countryOfficialUseStatus
Indicates the status or manner in which something (such as a language, symbol, or standard) is officially used or recognized by a country.
-
D.
hasISO3166-1NumericCode
Indicates that an entity is associated with a specific ISO 3166-1 numeric country code.
-
E.
countrySubdivisionStatus
Indicates the administrative or political status assigned to a specific subdivision within a country (such as state, province, or territory).
- 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e500528bb88190a9f9ba6428cc2076 |
completed | April 19, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69e44fd81c788190b08c6be3b07a08c5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.