Triple
T2989000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacobean Revival |
E80698
|
entity |
| Predicate | basedOnPeriod |
P4343
|
FINISHED |
| Object | early 17th-century English architecture |
—
|
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: early 17th-century English architecture | Statement: [Jacobean Revival, basedOnPeriod, early 17th-century English architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnPeriod Context triple: [Jacobean Revival, basedOnPeriod, early 17th-century English architecture]
-
A.
refersToPeriod
chosen
Indicates that one entity designates, references, or is associated with a specific time period or interval.
-
B.
areBasedOn
Indicates that one entity is founded, derived, or developed from the principles, content, or structure of another entity.
-
C.
basedOnEvent
Indicates that something is derived from, influenced by, or determined in reference to a specific event.
-
D.
basedOnProcess
Indicates that something is derived from, determined by, or dependent on a particular process or sequence of actions.
-
E.
periodizedAs
Indicates that something has been divided or organized into distinct time periods according to a particular periodization scheme.
- 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_69ad8b16c3488190b47b6aa7a59a335b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99dcdb00819092ca5f10396408e0 |
completed | March 8, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ad961403108190bbecb8d3608fd4e0 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:59 p.m.