Triple
T33564601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sharambeyan Street historic district |
E859720
|
entity |
| Predicate | eraOfArchitecture |
P68750
|
FINISHED |
| Object | 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: 19th century | Statement: [Sharambeyan Street historic district, eraOfArchitecture, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfArchitecture Context triple: [Sharambeyan Street historic district, eraOfArchitecture, 19th century]
-
A.
inArchitecturalMovement
Indicates that an architectural work, style, or practitioner belongs to or is associated with a specific architectural movement.
-
B.
eraOfOriginalMonuments
chosen
Indicates the historical time period during which the original monuments were created or first established.
-
C.
majorFigureInArchitecture
Indicates that an entity is recognized as a leading or highly influential figure within the field of architecture.
-
D.
architecturalOrigin
Indicates the place, style, or tradition from which an architectural work or design originates.
-
E.
architecturalInfluence
Indicates that one architectural style, structure, or designer has had a formative impact on the design, style, or features of another.
- 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_69f3497c1d288190a844ea699914e038 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: May 1, 2026, 1:40 a.m.