Triple
T29838641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Hundred Years of Photography 1839–1939 |
E757723
|
entity |
| Predicate | startOfTimeSpanCovered |
P9200
|
FINISHED |
| Object | 1839 |
—
|
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: 1839 | Statement: [A Hundred Years of Photography 1839–1939, startOfTimeSpanCovered, 1839]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfTimeSpanCovered Context triple: [A Hundred Years of Photography 1839–1939, startOfTimeSpanCovered, 1839]
-
A.
timePeriodCoveredTo
Indicates the span or duration of time that is encompassed, addressed, or relevant to a given subject or entity.
-
B.
coversPeriodStart
chosen
Indicates that the time span or coverage of one entity begins at, or includes, the specified starting point in time of another entity or period.
-
C.
recordedInPeriodStart
Indicates that an event or record began or was first documented at the start of a specified time period.
-
D.
timeSpanEndsBefore
Indicates that one time span concludes entirely before the starting point of another time span, with no overlap between them.
-
E.
timeSpanIncludes
Indicates that one time span fully contains or covers the entire duration of another time span.
- 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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fe8ddf70e48190a917eb9e8f7b6966 |
completed | May 9, 2026, 1:29 a.m. |
| PD | Predicate disambiguation | batch_69fe87ef94dc81909bb00ec8d6de9bcd |
completed | May 9, 2026, 1:03 a.m. |
Created at: April 29, 2026, 5:38 p.m.