Triple
T28306920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rambaldi prophecy |
E713881
|
entity |
| Predicate | inUniverseTimePeriodOfAuthor |
P102057
|
FINISHED |
| Object | Renaissance |
—
|
NE NERFINISHED |
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: Renaissance | Statement: [Rambaldi prophecy, inUniverseTimePeriodOfAuthor, Renaissance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseTimePeriodOfAuthor Context triple: [Rambaldi prophecy, inUniverseTimePeriodOfAuthor, Renaissance]
-
A.
workPeriodOfAuthorDescribed
Indicates that the time period during which an author was active or produced work is being described.
-
B.
workAuthoredInUniverse
chosen
Indicates that a creative work is set within, or narratively belongs to, a particular fictional or conceptual universe.
-
C.
authorLifespanContext
Indicates the temporal or historical context of an author’s life span in relation to other events, periods, or entities.
-
D.
eraOfAuthor
Indicates the historical time period or era during which an author lived or produced their work.
-
E.
hasAuthorAtTimeOfWriting
Indicates that a work is associated with a specific author as they were at the particular time the work was written.
- 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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 11:38 p.m.