Triple
T17728798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lily |
E442534
|
entity |
| Predicate | setInWorkTimePeriod |
P56370
|
FINISHED |
| Object | 1950s |
—
|
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: 1950s | Statement: [Lily, setInWorkTimePeriod, 1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setInWorkTimePeriod Context triple: [Lily, setInWorkTimePeriod, 1950s]
-
A.
setInWorkBy
Indicates that something (such as a scene, event, or element) is situated or occurs within the context or setting of a particular work (such as a book, film, or other creative production).
-
B.
setWorkIn
Indicates that an entity assigns or places a work, task, or project into a particular context, location, or setting.
-
C.
containsWorkFromPeriod
Indicates that something includes or features work that originates from a specified historical or temporal period.
-
D.
isSetInTimePeriod
chosen
Indicates that an event, story, or situation takes place within a specified time period.
-
E.
workSettingPeriod
Indicates the time period during which a particular work setting or employment context is in effect.
- 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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e478e4ae5c8190a6f0743f7e74b5bf |
completed | April 19, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:08 a.m.