Triple
T30992226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regio VI of Pompeii |
E789695
|
entity |
| Predicate | timeOfMaximumOccupation |
P178418
|
FINISHED |
| Object | 1st century AD |
—
|
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: 1st century AD | Statement: [Regio VI of Pompeii, timeOfMaximumOccupation, 1st century AD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfMaximumOccupation Context triple: [Regio VI of Pompeii, timeOfMaximumOccupation, 1st century AD]
-
A.
peakOccupation
chosen
Indicates the time or context in which an entity reaches its highest level of activity, usage, or occupancy.
-
B.
timeOfPeakSize
Indicates the specific time at which something reaches its maximum size or extent.
-
C.
hasNumberOfSeatsAtPeak
Indicates the maximum number of seats available or occupied at the peak usage or capacity of something.
-
D.
numberOfEmployeesAtPeak
Indicates the highest recorded count of employees that an entity had at any point in time.
-
E.
deploymentPeakNumber
Indicates the maximum number of deployments (or deployment instances) reached during a specified period or under given conditions.
- 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_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: April 29, 2026, 8:56 p.m.