Triple
T1782726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brill streetcar |
E39323
|
entity |
| Predicate | heritageUse |
P28383
|
FINISHED |
| Object | tourist tram services |
—
|
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: tourist tram services | Statement: [Brill streetcar, heritageUse, tourist tram services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageUse Context triple: [Brill streetcar, heritageUse, tourist tram services]
-
A.
heritageValue
Indicates that something possesses cultural, historical, or traditional significance that is valued and preserved as heritage.
-
B.
heritageManagement
Indicates the management, preservation, and regulation of cultural or natural heritage resources by responsible entities.
-
C.
heritageFunction
chosen
Indicates the role, use, or purpose that a heritage asset or element serves within its cultural, historical, or social context.
-
D.
heritageType
Indicates the classification of an entity’s cultural or natural heritage category or type within a heritage framework.
-
E.
heritageReference
Indicates that one entity serves as a cultural, historical, or heritage-related reference or source for another entity.
- 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_69a88630519c8190a17addd83c4a3ef4 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab74dc9d1481908084ef07872a71f8 |
completed | March 7, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69aa61cf3ca881908641fd73ce2f7c9d |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.