Triple
T31077714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vicus Caprarius |
E792010
|
entity |
| Predicate | foundInMunicipio |
P173321
|
FINISHED |
| Object | Municipio I of Rome |
—
|
NE NERFINISHED |
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: [Vicus Caprarius, foundInMunicipio, Municipio I of Rome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundInMunicipio Context triple: [Vicus Caprarius, foundInMunicipio, Municipio I of Rome]
-
A.
isMunicipalHomeOf
Indicates that a municipality serves as the official home base or hosting location for a particular entity or organization.
-
B.
inComarca
Indicates that one entity is located within or belongs to the jurisdiction or territory of a specific comarca (administrative district or region).
-
C.
isMunicipalBarrioOf
chosen
Indicates that a specific barrio (neighborhood or district) belongs administratively to, or is part of, a particular municipality.
-
D.
municipioPrincipal
Indicates that one municipality serves as the main or principal municipality in relation to another entity or area.
-
E.
locatedInPresentDayMunicipality
Indicates that an entity is situated within the boundaries of a specific municipality as it exists in the present day, regardless of historical administrative changes.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: April 29, 2026, 9:02 p.m.