Triple
T19134704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Francesca da Rimini |
E468405
|
entity |
| Predicate | firstAppearanceYearApproximate |
P4114
|
FINISHED |
| Object | c. 1308–1321 |
—
|
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. 1308–1321 | Statement: [Francesca da Rimini, firstAppearanceYearApproximate, c. 1308–1321]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstAppearanceYearApproximate Context triple: [Francesca da Rimini, firstAppearanceYearApproximate, c. 1308–1321]
-
A.
firstAppearanceApprox
Indicates that one entity is the approximate or estimated first appearance of another entity in time or context.
-
B.
firstPublicationYearOfAppearance
Indicates the year in which an entity (such as a work or character) first appeared in a published form.
-
C.
firstAppearedAt
Indicates the point in time or specific event at which an entity was first introduced, observed, or became known.
-
D.
yearOfFirstApparition
Indicates the calendar year in which the entity first appeared or was introduced.
-
E.
firstAppeared
chosen
Indicates the earliest known time or context in which an entity was introduced, observed, or came into existence.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3ec4c848190af450bf5bf8db5e7 |
completed | April 20, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.