Triple
T21184189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simbirsk |
E522034
|
entity |
| Predicate | historicalArchitectureType |
P5929
|
FINISHED |
| Object | wooden buildings |
—
|
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: wooden buildings | Statement: [Simbirsk, historicalArchitectureType, wooden buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalArchitectureType Context triple: [Simbirsk, historicalArchitectureType, wooden buildings]
-
A.
historicalStructure
Indicates that the subject is a structure recognized for its historical significance or heritage value.
-
B.
historicStructureArchitect
Indicates that an architect is the designer or primary planner responsible for a particular historic structure.
-
C.
historicLocationType
Indicates the specific kind or category of a place based on its historical significance or role.
-
D.
architectureHistory
Indicates a historical or developmental relationship between an entity and its architectural evolution, style, or significant architectural events over time.
-
E.
heritageType
chosen
Indicates the classification of an entity’s cultural or natural heritage category or type within a heritage framework.
- 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_69e0b50ef1d48190b063aa342667df22 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e730205ce88190b0bb33003295d6e7 |
completed | April 21, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:05 p.m.