Triple
T23860081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MF |
E592420
|
entity |
| Predicate | hasAlpha3CodeOfRepresentedEntity |
P43262
|
FINISHED |
| Object | MAF |
—
|
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: MAF | Statement: [MF, hasAlpha3CodeOfRepresentedEntity, MAF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlpha3CodeOfRepresentedEntity Context triple: [MF, hasAlpha3CodeOfRepresentedEntity, MAF]
-
A.
hasISO3166Alpha3Code
chosen
Indicates that an entity is associated with a specific three-letter country code defined by the ISO 3166-1 alpha-3 standard.
-
B.
hasISO4217ThreeLetterCode
Indicates that an entity is associated with a specific three-letter currency code defined by the ISO 4217 standard.
-
C.
hasISO3166-1NumericCode
Indicates that an entity is associated with a specific ISO 3166-1 numeric country code.
-
D.
sharesISO3166CodeWith
Indicates that two entities are associated with and use the same ISO 3166 country code.
-
E.
ISOCode
Indicates that an entity is associated with a specific standardized code defined by the International Organization for Standardization (ISO).
- 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_69e25d22eb488190914b193aff952e83 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cadebc6481909110a2a5fe85c93f |
completed | April 29, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:12 p.m.