Triple
T26603187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolis of Aix-Marseille-Provence |
E667693
|
entity |
| Predicate | ISOCodeLike |
P208
|
FINISHED |
| Object | FR-AMP |
—
|
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: FR-AMP | Statement: [Metropolis of Aix-Marseille-Provence, ISOCodeLike, FR-AMP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISOCodeLike Context triple: [Metropolis of Aix-Marseille-Provence, ISOCodeLike, FR-AMP]
-
A.
ISOCode
chosen
Indicates that an entity is associated with a specific standardized code defined by the International Organization for Standardization (ISO).
-
B.
ISOCodeContext
Indicates the contextual framework or domain within which a particular ISO code is defined, interpreted, or applied.
-
C.
ISO3166-1Code
Indicates the standardized two- or three-letter country or territory code assigned under the ISO 3166-1 international standard.
-
D.
iso3166CodeBasedOn
Indicates that one code or designation is derived from, corresponds to, or is assigned on the basis of a specific ISO 3166 country or region code.
-
E.
isocodeCategory
Indicates that an entity is classified under a specific ISO code category or grouping.
- 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_69ee9cfd20348190bb1255d2603efb7a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6157198fc819083151a884187abae |
completed | May 2, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 2:13 a.m.