Triple
T23936339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Culgaith railway station |
E602647
|
entity |
| Predicate | currentUseOfBuildings |
P147436
|
FINISHED |
| Object | private residence |
—
|
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: private residence | Statement: [Culgaith railway station, currentUseOfBuildings, private residence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentUseOfBuildings Context triple: [Culgaith railway station, currentUseOfBuildings, private residence]
-
A.
currentBuildingUse
chosen
Indicates the present functional purpose or activity for which a building is being used.
-
B.
currentBuildings
Indicates that certain buildings are presently existing, active, or in use at a given time or context.
-
C.
previousBuildingUse
Indicates that a building previously served a specified use or function before its current one.
-
D.
buildings
Indicates that one or more buildings are associated with, located at, or relevant to the referenced entity.
-
E.
buildingUsedBy
Indicates that a particular building is utilized or occupied by a specified entity for some purpose.
- 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_69e2953cf6e081909b8e25a10a52dddc |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1cfa063088190bdbe2dacf854f8b5 |
completed | April 29, 2026, 9:30 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:04 p.m.