Triple
T30107955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ε 201 |
E765181
|
entity |
| Predicate | hasOriginalDateRange |
P46071
|
FINISHED |
| Object | early 5th 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: early 5th century | Statement: [ε 201, hasOriginalDateRange, early 5th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalDateRange Context triple: [ε 201, hasOriginalDateRange, early 5th century]
-
A.
hasBaseDate
Indicates that an entity is associated with a specific reference or starting date used as the basis for related calculations, schedules, or validity periods.
-
B.
hasOriginalVersion
Indicates that one entity is the original or initial version from which another entity is derived or adapted.
-
C.
hasDateWith
Indicates that one entity is scheduled to go on or is engaged in a romantic or social date with another entity.
-
D.
representsDateRange
chosen
Indicates that a subject is associated with, valid for, or applicable during a specific start-to-end date range.
-
E.
hasGregorianDateRange
Indicates that an entity is associated with a specific start and end date expressed in the Gregorian calendar.
- 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: April 29, 2026, 7:09 p.m.