Triple
T9668899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Busento River (legendary) |
E233975
|
entity |
| Predicate | timeOfLegendaryEvent |
P20414
|
FINISHED |
| Object | circa 410 |
—
|
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: circa 410 | Statement: [Busento River (legendary), timeOfLegendaryEvent, circa 410]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfLegendaryEvent Context triple: [Busento River (legendary), timeOfLegendaryEvent, circa 410]
-
A.
timeOfEventCommemorated
Indicates the specific time or date at which the event being commemorated originally occurred.
-
B.
capitalEventDate
Indicates the date on which a capital-related event (such as establishment, designation, or change of capital status) occurred.
-
C.
timeExistence
Indicates the period or duration during which an entity exists or is valid.
-
D.
timeSinceEventCommemorated
Indicates the amount of time that has passed since a particular event was commemorated.
-
E.
timeInMyth
chosen
Indicates that an entity exists or occurs during a specific time period within a mythological narrative or tradition.
- 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_69ca848f55e48190b3f67252571c3d45 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c3d5b3481908c8c66a3528875aa |
completed | April 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b3239c8190b3ae3b9bd121e4bd |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:15 p.m.