Triple
T19216410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | biography of Isis |
E480496
|
entity |
| Predicate | sourceWorkDate |
P90615
|
FINISHED |
| Object | circa 1360 |
—
|
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 1360 | Statement: [biography of Isis, sourceWorkDate, circa 1360]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceWorkDate Context triple: [biography of Isis, sourceWorkDate, circa 1360]
-
A.
associatedWorkDate
chosen
Indicates the date on which a related or associated work (such as a publication, performance, or creation) is linked to the subject entity.
-
B.
sourceWorkFirstPerformed
Indicates the original performance event or context in which a work was first publicly performed.
-
C.
hasSourceWork
Indicates that something originates from, is derived from, or is based on a particular source work.
-
D.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
E.
sourceWorkSection
Indicates that one entity is a specific section or part extracted from a larger source work.
- 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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fa3aff9c8190974363683b8246f5 |
completed | April 20, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69e4dcf22b3c8190bee02e3af946e114 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:22 p.m.