Triple
T19265259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spadina House |
E481757
|
entity |
| Predicate | hasPeriodRepresentation |
P4343
|
FINISHED |
| Object | 1900s |
—
|
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: 1900s | Statement: [Spadina House, hasPeriodRepresentation, 1900s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPeriodRepresentation Context triple: [Spadina House, hasPeriodRepresentation, 1900s]
-
A.
hasPeriodRange
Indicates that there is a temporal span or interval during which something is valid, active, or applicable.
-
B.
refersToPeriod
chosen
Indicates that one entity designates, references, or is associated with a specific time period or interval.
-
C.
includesPeriodFeature
Indicates that something contains or incorporates a specific period-related feature as part of its characteristics or structure.
-
D.
hasBinaryPeriod
Indicates that two objects in a binary system have a specific orbital period for completing one full revolution around their common center of mass.
-
E.
hasLanguagePeriod
Indicates a relationship where a language is associated with a specific historical or temporal period during which it was used or recognized.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb8ca2e88190baad3b6c199ee036 |
completed | April 20, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:29 p.m.