Triple
T9398266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Province of Cremona |
E226400
|
entity |
| Predicate | hasISTATCode |
P58226
|
FINISHED |
| Object | 019 |
—
|
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: 019 | Statement: [Province of Cremona, hasISTATCode, 019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasISTATCode Context triple: [Province of Cremona, hasISTATCode, 019]
-
A.
inseeCode
Indicates the official INSEE (French national statistics institute) code assigned to an entity, typically identifying a specific geographic or administrative unit.
-
B.
hasGovernorateCode
Indicates that an entity is associated with a specific governorate through a designated code.
-
C.
hasNationalLocationCode
chosen
Indicates that an entity is associated with a specific national location code that identifies its location within a country’s coding system.
-
D.
hasStationCode
Indicates that an entity is associated with a specific station identification code.
-
E.
isCapitalCodeFor
Indicates that one code or abbreviation serves as the official capital designation for a particular region, country, or administrative entity.
- 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_69ca843170f88190800a8ab2b5fc568e |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd51541020819097da2eb60be73760 |
completed | April 1, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69cca545b2448190a4297312e39c21ac |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:46 p.m.