Triple
T8616471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Gallery |
E204050
|
entity |
| Predicate | typicalCollectionPeriodStart |
P83909
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [New Gallery, typicalCollectionPeriodStart, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCollectionPeriodStart Context triple: [New Gallery, typicalCollectionPeriodStart, late 19th century]
-
A.
typicalStartPeriod
Indicates the usual or standard time period during which something begins or is initiated.
-
B.
startDateOfCollection
Indicates the calendar date on which a particular collection or collecting activity begins.
-
C.
typicalEndDate
Indicates the date on which something, such as an event, process, or period, normally or customarily ends.
-
D.
usePeriodStart
Indicates that an entity begins to be used or becomes active starting from a specified time period.
-
E.
effectivePeriodStart
Indicates the date and time when a specified condition, status, or agreement becomes valid or goes into effect.
- F. None of above. chosen
Provenance (4 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_69ca832ceab8819096e4a9f546695079 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc4703b57c81909511de72fa5c38d7 |
completed | March 31, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cc455437488190b7506f820daf6e32 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc46c330bc8190a9b644078881c6ff |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:25 p.m.