Triple
T20972868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sphere of Venus |
E516546
|
entity |
| Predicate | workCantoRange |
P138159
|
FINISHED |
| Object | Paradiso cantos 8–9 |
—
|
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: Paradiso cantos 8–9 | Statement: [Sphere of Venus, workCantoRange, Paradiso cantos 8–9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workCantoRange Context triple: [Sphere of Venus, workCantoRange, Paradiso cantos 8–9]
-
A.
hasEmployeeRange
Indicates the range or limits on the number of employees associated with an entity.
-
B.
appearsInWorkRange
chosen
Indicates that an entity is featured or occurs within a specified range or subset of a larger work or collection of works.
-
C.
timePeriodOfWorks
Indicates the span of time during which the associated works were created, produced, or active.
-
D.
hasNumberWithinWork
Indicates that a specific number or numeric value is contained, referenced, or used within a particular work (such as a document, publication, or creative piece).
-
E.
workPeriod
Indicates the span of time during which an entity is engaged in a particular work or employment activity.
- 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_69e0b4fee5ac8190875fa9ceba1a5e5e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fba161d88190b8905891f449004e |
completed | April 21, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:45 p.m.