Triple
T19046425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Two Figures at Desk |
E466144
|
entity |
| Predicate | hasCreatorLifespan |
P27074
|
FINISHED |
| Object | 1885–1965 |
—
|
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: 1885–1965 | Statement: [Two Figures at Desk, hasCreatorLifespan, 1885–1965]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCreatorLifespan Context triple: [Two Figures at Desk, hasCreatorLifespan, 1885–1965]
-
A.
creatorLifespan
chosen
Indicates the time period between the birth and death of the creator associated with an entity.
-
B.
timeSpanOfCreation
Indicates the period of time during which the creation of an entity took place.
-
C.
hasLifetimeStatus
Indicates that an entity is associated with a status or condition that applies for the entire duration of its existence.
-
D.
authorLifespanContext
Indicates the temporal or historical context of an author’s life span in relation to other events, periods, or entities.
-
E.
createdFor
Indicates that one entity was made, produced, or designed specifically to serve, benefit, or be used by 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d80466f88190988171920f2be7dc |
completed | April 20, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.