Triple
T14821242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victoria Lucas |
E348456
|
entity |
| Predicate | usedDuringAuthorLifetime |
P4341
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Victoria Lucas, usedDuringAuthorLifetime, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedDuringAuthorLifetime Context triple: [Victoria Lucas, usedDuringAuthorLifetime, true]
-
A.
hasAuthorAtTimeOfWriting
Indicates that a work is associated with a specific author as they were at the particular time the work was written.
-
B.
authorLifespanContext
Indicates the temporal or historical context of an author’s life span in relation to other events, periods, or entities.
-
C.
livedDuring
Indicates that the subject existed or was alive at some point within the time period or lifespan associated with the object.
-
D.
dateOfAuthorDeathBeforePublication
Indicates that the author of a work died before that work was published.
-
E.
usedDuring
chosen
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
- 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decfe64328819083ce42704cf0602d |
completed | April 14, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69de8c0ef8a4819092d84478b1f56db1 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:50 a.m.