Triple
T13492687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regola |
E320674
|
entity |
| Predicate | hasRioneNumber |
P8975
|
FINISHED |
| Object | VII |
—
|
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: VII | Statement: [Regola, hasRioneNumber, VII]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRioneNumber Context triple: [Regola, hasRioneNumber, VII]
-
A.
hasMunicipalDistrictNumber
Indicates that a municipality or local administrative unit is assigned a specific district number within its municipal structure.
-
B.
hasUnitNumber
Indicates that an entity is associated with a specific unit identifier or number within a larger building, complex, or organizational structure.
-
C.
boroughNumber
chosen
Indicates the numerical identifier assigned to a specific borough within a larger administrative or municipal division.
-
D.
hasConnectingRoadNumber
Indicates that there exists a road connection between two locations or road segments identified by a specific road number.
-
E.
hasJunctionNumber
Indicates that a road, route, or similar pathway is assigned a specific junction or exit number.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf4c66008190b287e0551889d7c8 |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:43 p.m.