Triple
T8418334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hollingbourne |
E198783
|
entity |
| Predicate | hasTraditionalRoofMaterial |
P29245
|
FINISHED |
| Object | Kent peg tiles |
—
|
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: Kent peg tiles | Statement: [Hollingbourne, hasTraditionalRoofMaterial, Kent peg tiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalRoofMaterial Context triple: [Hollingbourne, hasTraditionalRoofMaterial, Kent peg tiles]
-
A.
hasTypeOfRoof
Indicates that an entity possesses or is characterized by a specific kind or style of roof.
-
B.
roofMaterialOriginal
Indicates the material that was originally used to construct the roof of a structure.
-
C.
buildingMaterialTradition
chosen
Indicates the customary or historically established use of particular materials in the construction of a building or structure.
-
D.
traditionallyBuiltOver
Indicates that one entity has been constructed on top of another in a manner consistent with long-established or customary building practices.
-
E.
traditionallyHouses
Indicates that one entity has historically or customarily served as the location or container 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_69ca8312d63c8190bf133b676b44a385 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb84c7d6e48190a2bbde89c5d42af6 |
completed | March 31, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69cb70d70ea081909c3dc1bd2ec14f85 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:06 p.m.