Triple
T20011959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oberon |
E494609
|
entity |
| Predicate | timeOfWorkPublication |
P137798
|
FINISHED |
| Object | late 16th century |
—
|
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: late 16th century | Statement: [Oberon, timeOfWorkPublication, late 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfWorkPublication Context triple: [Oberon, timeOfWorkPublication, late 16th century]
-
A.
timeFromEventToPublication
Indicates the duration between when an event occurs and when it is published or reported.
-
B.
timePeriodOfWorks
chosen
Indicates the span of time during which the associated works were created, produced, or active.
-
C.
workedForPublication
Indicates that an entity was employed by or contributed work to a particular publication (such as a newspaper, magazine, or journal).
-
D.
createdInWorkPublishedIn
Indicates that something was created within a work that was subsequently published in a particular publication or venue.
-
E.
workInThisPublication
Indicates that an entity performs work or contributes within the context of the specified publication.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6623773d88190826616a02d3c3e69 |
completed | April 20, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:34 p.m.