Triple
T29421377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FI |
E746164
|
entity |
| Predicate | countryISOStatus |
P198803
|
FINISHED |
| Object | officially assigned code element |
—
|
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: officially assigned code element | Statement: [FI, countryISOStatus, officially assigned code element]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryISOStatus Context triple: [FI, countryISOStatus, officially assigned code element]
-
A.
countryStatus
Indicates the political or legal condition of a country, such as its sovereignty, recognition, or current state in international or domestic contexts.
-
B.
countrySpecificStatus
Indicates a status or condition that is defined or applied specifically in the context of a particular country.
-
C.
provinceISOCode
Indicates the standardized ISO code assigned to the province associated with the subject entity.
-
D.
countryDeJure
Indicates that one entity is the legally recognized (de jure) country having sovereignty or authority over another entity.
-
E.
hasISO3166-1NumericCode
Indicates that an entity is associated with a specific ISO 3166-1 numeric country code.
- 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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69ff0b6bc4a88190bf1d38c6ea26bcdc |
completed | May 9, 2026, 10:24 a.m. |
| PD | Predicate disambiguation | batch_69ff082a22f4819095ded971dbd8ea7b |
completed | May 9, 2026, 10:10 a.m. |
| PDg | Predicate description generation | batch_69ff0b6a541c8190a6fa847552f3491f |
completed | May 9, 2026, 10:24 a.m. |
Created at: April 28, 2026, 3:06 p.m.