Triple
T896723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Divine Comedy |
E19361
|
entity |
| Predicate | approximateEndOfComposition |
P8204
|
FINISHED |
| Object | c. 1320 |
—
|
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: c. 1320 | Statement: [Divine Comedy, approximateEndOfComposition, c. 1320]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateEndOfComposition Context triple: [Divine Comedy, approximateEndOfComposition, c. 1320]
-
A.
hasApproximateEnd
chosen
Indicates that an entity’s end point, time, or boundary is known only approximately rather than precisely.
-
B.
endedWith
Indicates that one event, process, or state concluded with or was finalized by another specified event, condition, or outcome.
-
C.
rangeEnd
Indicates the endpoint or upper boundary value of a specified range in a relationship or measurement.
-
D.
productionEnd
Indicates that a production process, activity, or run has come to its completion or final stopping point.
-
E.
lastPrintableCharacter
Indicates that one character is the final non-whitespace (or otherwise displayable) character in a given sequence or string.
- 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_69a4939d37188190848be3d426ebc9ae |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad2550c88190a624eb5627d472ad |
completed | March 1, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69a4aa94f7c881908deeb62308942e19 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.