Triple
T3311842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Launceston |
E69589
|
entity |
| Predicate | hasHeritageBuildings |
P42084
|
FINISHED |
| Object | Victorian-era 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: Victorian-era architecture | Statement: [Launceston, hasHeritageBuildings, Victorian-era architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeritageBuildings Context triple: [Launceston, hasHeritageBuildings, Victorian-era architecture]
-
A.
hasHeritageFeature
Indicates that an entity possesses or includes a feature recognized as part of cultural, historical, or natural heritage.
-
B.
hasHeritage
Indicates that an entity possesses or is associated with a particular cultural, ethnic, or ancestral background.
-
C.
hasPreservedBuildings
chosen
Indicates that an entity possesses buildings that have been maintained or kept in their original or historical condition.
-
D.
heritageType
Indicates the classification of an entity’s cultural or natural heritage category or type within a heritage framework.
-
E.
residenceHistoric
Indicates that a residence has historical significance or is formally recognized as a historic dwelling.
- 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_69ad859f218081909458d2cebbf57565 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0eddf488190b7f05b3903b96d4b |
completed | March 8, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69ada4282730819092aa39c5f9269df0 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.