Triple
T14127499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucilius Bassus |
E340070
|
entity |
| Predicate | approximateActivityEndCentury |
P112910
|
FINISHED |
| Object | 1st century |
—
|
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 | Statement: [Lucilius Bassus, approximateActivityEndCentury, 1st century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateActivityEndCentury Context triple: [Lucilius Bassus, approximateActivityEndCentury, 1st century]
-
A.
approximateUseEndCentury
Indicates that something’s period of use ended around, but not necessarily exactly in, a specified century.
-
B.
approximateStartCentury
Indicates the century in which something is estimated or roughly believed to have begun.
-
C.
approximateUseEndCenturyBC
Indicates an estimated century BCE by which the use or activity associated with the subject is believed to have ended.
-
D.
estimatedConstructionEndCentury
Indicates the century in which the construction of something is estimated to have been completed.
-
E.
approximateStartCenturyBC
Indicates that an entity’s starting time or occurrence is approximately located within a specified century before the Common Era (BC).
- F. None of above. chosen
Provenance (4 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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de6098013c8190b1bac9d3fff60acd |
completed | April 14, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:22 p.m.