Triple
T1610112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 3166-2:PK |
E34596
|
entity |
| Predicate | firstPartFormat |
P30244
|
FINISHED |
| Object | ISO 3166-1 alpha-2 code of Pakistan |
—
|
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 3166-1 alpha-2 code of Pakistan | Statement: [ISO 3166-2:PK, firstPartFormat, ISO 3166-1 alpha-2 code of Pakistan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPartFormat Context triple: [ISO 3166-2:PK, firstPartFormat, ISO 3166-1 alpha-2 code of Pakistan]
-
A.
firstReleaseFormat
Indicates the original medium or format in which something (such as a work or product) was first released.
-
B.
format
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
C.
firstLetter
Indicates that one entity is the initial character or starting letter of another entity (typically a string or word).
-
D.
firstPartPublicationYear
Indicates the year in which the first part or installment of a multi-part publication was released.
-
E.
firstSeasonFormat
Indicates the specific format or structure in which the first season of something (such as a series or competition) was originally presented.
- F. None of above. chosen
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_69a885ffc5ec819091afa325d5f9611c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93fa6926081908bc78d15c0be3185 |
completed | March 5, 2026, 8:32 a.m. |
| PD | Predicate disambiguation | batch_69a907c35f848190a2428c52e81d013e |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a93fa5aa04819084d1154ef900303f |
completed | March 5, 2026, 8:32 a.m. |
Created at: March 4, 2026, 7:28 p.m.