Triple
T21866647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regio XII Piscina Publica |
E539898
|
entity |
| Predicate | hadCensus |
P45218
|
FINISHED |
| Object | 4th century CE |
—
|
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: 4th century CE | Statement: [Regio XII Piscina Publica, hadCensus, 4th century CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadCensus Context triple: [Regio XII Piscina Publica, hadCensus, 4th century CE]
-
A.
census
chosen
Indicates that an official count or survey is conducted to determine the number and characteristics of a population within a defined area or group.
-
B.
hasCensusDay
Indicates the specific date on which a census is officially conducted or referenced for a given census event.
-
C.
hasCensusFunction
Indicates that an entity holds an official role or responsibility related to conducting, managing, or supporting census activities.
-
D.
censusReportedIn
Indicates that information about a population or demographic count is documented or recorded in a specific census.
-
E.
censusNumber
Indicates the unique identifier or count assigned to an entity within an official census record.
- 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_69e0c478f59081909d54302b57fc1ce3 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0d63f2ec48190956a3e99d8f98b1f |
completed | April 28, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:56 p.m.