Triple
T16478657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Fedele Intelvi |
E400255
|
entity |
| Predicate | administrativeStatusBeforeMerger |
P14579
|
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: [San Fedele Intelvi, administrativeStatusBeforeMerger, comune]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeStatusBeforeMerger Context triple: [San Fedele Intelvi, administrativeStatusBeforeMerger, comune]
-
A.
constitutionalStatusBeforeMerger
Indicates the constitutional or legal status an entity held prior to being merged into another entity or structure.
-
B.
governingBodyBeforeMerger
Indicates that one entity functioned as the governing body of another entity prior to a merger event.
-
C.
affiliationBeforeMerger
Indicates that an entity was affiliated with another entity prior to a merger event involving one or both of them.
-
D.
legalStatusBefore
Indicates the legal condition or classification that applied to an entity prior to a specified event, change, or point in time.
-
E.
formerAdministrativeStatus
chosen
Indicates that an entity previously held, but no longer holds, a particular administrative status or role.
- 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e01230881908b2147a25f78b7f4 |
completed | April 18, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69e22706b0588190a48a951c5211a617 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:13 a.m.