Triple
T35250523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Street of the Silversmiths |
E1018081
|
entity |
| Predicate | hasTypicalBuildingUse |
P200030
|
FINISHED |
| Object | workshops |
—
|
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: workshops | Statement: [Street of the Silversmiths, hasTypicalBuildingUse, workshops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalBuildingUse Context triple: [Street of the Silversmiths, hasTypicalBuildingUse, workshops]
-
A.
currentBuildingUse
Indicates the present functional purpose or activity for which a building is being used.
-
B.
secondaryBuildingUse
Indicates how a building is used in a secondary or supplementary capacity in addition to its primary function.
-
C.
intendedBuildingType
Indicates the type of building that something is planned or designed to be.
-
D.
usedOnPublicBuildings
Indicates that something is employed or applied in the context of public buildings, such as for their construction, operation, decoration, or maintenance.
-
E.
typicalSectorUse
Indicates the type of sector in which something is most commonly or characteristically used.
- F. None of above. chosen
Provenance (4 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_69f76de407d081909dfc3c419817ae93 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff6c061c6c81909ff485e9cafc88a2 |
completed | May 9, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ff6aaf886c8190a3c87d089453f3de |
completed | May 9, 2026, 5:11 p.m. |
| PDg | Predicate description generation | batch_69ff6c04fa208190b1fab40a71ef923f |
completed | May 9, 2026, 5:16 p.m. |
Created at: May 3, 2026, 4:02 p.m.