Triple
T22580344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vagaus |
E544548
|
entity |
| Predicate | timeOfCreationWork |
P116819
|
FINISHED |
| Object | 1716 |
—
|
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: 1716 | Statement: [Vagaus, timeOfCreationWork, 1716]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfCreationWork Context triple: [Vagaus, timeOfCreationWork, 1716]
-
A.
timeSpanOfCreation
chosen
Indicates the period of time during which the creation of an entity took place.
-
B.
createdForWorkBy
Indicates that something was created specifically for use in work or professional activities by a particular agent or person.
-
C.
createdWork
Indicates that an agent is responsible for bringing a work (such as a creative, intellectual, or produced artifact) into existence.
-
D.
timePeriodOfWorks
Indicates the span of time during which the associated works were created, produced, or active.
-
E.
createdTo
Indicates that one entity was brought into existence, produced, or designed specifically for the purpose, use, or function of another entity.
- 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_69e11e30d05481909df915354c89f0d6 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f15ff065308190bca9fb24b47757e6 |
completed | April 29, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69ee626e6bb08190ada4dd8b48cc0c43 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:53 p.m.