Triple
T6141910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kastoria |
E136980
|
entity |
| Predicate | hasHistoricBuildingMaterial |
P29245
|
FINISHED |
| Object | stone |
—
|
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: stone | Statement: [Kastoria, hasHistoricBuildingMaterial, stone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricBuildingMaterial Context triple: [Kastoria, hasHistoricBuildingMaterial, stone]
-
A.
hasHistoricalOccupationMaterial
Indicates that something is composed of or contains material evidence related to past occupations or uses by people.
-
B.
hasStationBuildingMaterial
Indicates that a station’s building is constructed from, or primarily composed of, a specified material.
-
C.
buildingMaterialTradition
chosen
Indicates the customary or historically established use of particular materials in the construction of a building or structure.
-
D.
hasPreservedBuildings
Indicates that an entity possesses buildings that have been maintained or kept in their original or historical condition.
-
E.
hasReconstructionMaterial
Indicates that something is associated with, composed of, or utilizes a particular material for its reconstruction.
- 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_69c008a2c6308190a56519b22d55d083 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05cb387ac8190a60579b59a741425 |
completed | March 22, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69c055f19b0c81908be34a00ab218723 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:16 p.m.