Triple
T9308596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regio IX Circus Flaminius |
E223951
|
entity |
| Predicate | regioNumber |
P19171
|
FINISHED |
| Object | IX |
—
|
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: IX | Statement: [Regio IX Circus Flaminius, regioNumber, IX]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regioNumber Context triple: [Regio IX Circus Flaminius, regioNumber, IX]
-
A.
regionNumber
chosen
Indicates that an entity is assigned to or associated with a specific numbered region within a larger spatial or organizational division.
-
B.
routeRegion
Indicates that a route is located within, passes through, or is associated with a particular geographic region.
-
C.
isRegion
Indicates that one entity functions as a geographic or administrative region associated with another entity.
-
D.
regionID
Indicates that an entity is associated with, located in, or belongs to a specific geographic or administrative region identified by this ID.
-
E.
region1
Indicates that one entity is the first or primary region associated with, containing, or encompassing another entity.
- 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_69ca8424d0f08190831e2e93c6533aeb |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd1daba67c819081d53545d67ef127 |
completed | April 1, 2026, 1:29 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:37 p.m.