Triple
T38077819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colonnacce |
E950767
|
entity |
| Predicate | cityAdministrativeArea |
P33663
|
FINISHED |
| Object | Municipio I of Rome |
E393596
|
NE 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: Municipio I of Rome | Statement: [Colonnacce, cityAdministrativeArea, Municipio I of Rome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityAdministrativeArea Context triple: [Colonnacce, cityAdministrativeArea, Municipio I of Rome]
-
A.
cityAdministrativeRegion
Indicates that a city is located within or governed by a specific administrative region (such as a state, province, or similar jurisdiction).
-
B.
districtAdministration
Indicates that an entity is responsible for managing, governing, or overseeing the administrative affairs of a specific district or local jurisdiction.
-
C.
cityOrDistrict
Indicates that the subject is classified as either a city or a district in relation to the object.
-
D.
administrativeDistrictOf
chosen
Indicates that one entity serves as the administrative district or jurisdictional area governing or encompassing another entity.
-
E.
cityOrArea
Indicates that the subject is a city or a broader geographic area associated with the object.
- F. None of above.
Provenance (4 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_69f76f02a6c48190a94f3c0b3ee90cf2 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a415d4820c08190846c716a2bb8e212 |
completed | June 28, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.