Triple
T35092992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Justin |
E1012781
|
entity |
| Predicate | circaDateOfWork |
P13262
|
FINISHED |
| Object | 2nd–3rd century AD (approximate) |
—
|
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: 2nd–3rd century AD (approximate) | Statement: [Justin, circaDateOfWork, 2nd–3rd century AD (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: circaDateOfWork Context triple: [Justin, circaDateOfWork, 2nd–3rd century AD (approximate)]
-
A.
circaPeriodDescribed
Indicates that an entity is associated with or described as belonging to an approximate time period rather than an exact date.
-
B.
approximateYearWritten
Indicates the estimated calendar year in which something was written, when the exact year is not known.
-
C.
yearCirca
Indicates that the associated year is approximate or uncertain rather than exact.
-
D.
approximateDepictionDate
Indicates the estimated or inferred date when a depiction was created, rather than a precise, confirmed date.
-
E.
estimatedYearOfCreation
chosen
Indicates the year in which something is believed or approximated to have been created, rather than a precisely known creation year.
- 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_69f76dd432ec8190969bc32acfc152b1 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.