Triple
T33838508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hydatius of Aquae Flaviae |
E867298
|
entity |
| Predicate | chronicleTimeSpan |
P103499
|
FINISHED |
| Object | late 4th 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: late 4th century | Statement: [Hydatius of Aquae Flaviae, chronicleTimeSpan, late 4th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronicleTimeSpan Context triple: [Hydatius of Aquae Flaviae, chronicleTimeSpan, late 4th century]
-
A.
chronicleScope
chosen
Indicates the temporal or contextual span over which an event, process, or narrative is recorded or documented.
-
B.
collectionTimespan
Indicates the time period over which a collection exists, is accumulated, or is considered valid.
-
C.
timeSpanMentioned
Indicates that a specific duration or period of time is explicitly referenced in the context.
-
D.
timeSpanIncludes
Indicates that one time span fully contains or covers the entire duration of another time span.
-
E.
chronologicallyBetween
Indicates that one event or time point occurs after a first reference point and before a second reference point in temporal order.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
Created at: May 1, 2026, 1:47 a.m.