Triple
T30992187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regio VI of Pompeii |
E789695
|
entity |
| Predicate | streetSystem |
P3374
|
FINISHED |
| Object | orthogonal street grid |
—
|
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: orthogonal street grid | Statement: [Regio VI of Pompeii, streetSystem, orthogonal street grid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetSystem Context triple: [Regio VI of Pompeii, streetSystem, orthogonal street grid]
-
A.
roadSystem
Indicates a relationship where multiple roads are organized and connected as part of a larger, integrated transportation network or infrastructure.
-
B.
streetNetwork
chosen
Indicates the layout and connectivity relationships among streets within a geographic area, including how roads intersect, link, and form a navigable network.
-
C.
roadSystemPattern
Indicates the characteristic layout or organizational pattern of a road network within a given area.
-
D.
streetSet
Indicates that a particular street belongs to, or is included within, a specified set or collection of streets.
-
E.
roadSystemLevel
Indicates the classification or hierarchy level of a road within a broader transportation or road network system.
- 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_69f224c550b081909ddfceb0c3d03bdd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:56 p.m.