Triple
T35804209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shoin-zukuri |
E1035062
|
entity |
| Predicate | emergedCentury |
P113028
|
FINISHED |
| Object | 15th 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: 15th century | Statement: [Shoin-zukuri, emergedCentury, 15th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emergedCentury Context triple: [Shoin-zukuri, emergedCentury, 15th century]
-
A.
emergedByCentury
chosen
Indicates that something came into existence, became prominent, or first appeared during a specified century.
-
B.
century
Indicates that an entity is associated with, occurs in, or belongs to a particular 100-year time period.
-
C.
latestCentury
Indicates that the associated time or event occurs in, or belongs to, the most recent century relative to a given reference point.
-
D.
discoveredInCentury
Indicates that an entity was discovered during a specific century.
-
E.
collapseCentury
Indicates that one time period or event causes or undergoes a breakdown or compression of its century-level temporal distinction, effectively merging or reducing it into a different or broader timeframe.
- 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_69f76e169bd081909f16cd8c9ee7870c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:06 p.m.