Triple
T14673374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarano |
E344569
|
entity |
| Predicate | hasLocalAdministrativeLevel |
P80007
|
FINISHED |
| Object | comune |
—
|
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: comune | Statement: [Tarano, hasLocalAdministrativeLevel, comune]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalAdministrativeLevel Context triple: [Tarano, hasLocalAdministrativeLevel, comune]
-
A.
sharesAdministrativeLevel
Indicates that two entities are associated with the same tier or rank within an administrative or governmental hierarchy.
-
B.
isPartOfAdministrativeLevel
Indicates that one administrative unit is contained within or belongs to a higher-level administrative division in a governance hierarchy.
-
C.
hasAdministrativeArea
Indicates that one entity serves as the governing or jurisdictional area responsible for administering another entity.
-
D.
hasMunicipalLevel
chosen
Indicates that an entity is associated with a specific level or tier within a municipal (local government) hierarchy.
-
E.
hasHigherLevelSubdivision
Indicates that one administrative or organizational unit is contained within and subordinate to a larger, higher-level subdivision.
- 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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb55064cc8190b9669d0b2da61825 |
completed | April 14, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:27 a.m.