Triple
T15638486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Bath |
E376004
|
entity |
| Predicate | waterproofingMethod |
P119564
|
FINISHED |
| Object | bitumen layer between bricks |
—
|
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: bitumen layer between bricks | Statement: [Great Bath, waterproofingMethod, bitumen layer between bricks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterproofingMethod Context triple: [Great Bath, waterproofingMethod, bitumen layer between bricks]
-
A.
waterTolerance
Indicates the degree to which an entity can withstand or function effectively in the presence of water.
-
B.
floodResistanceDesign
Indicates that something is designed or engineered to withstand, mitigate, or remain functional during flooding conditions.
-
C.
watertightIntegrity
Indicates that one entity maintains a seal or barrier that prevents the passage or leakage of water relative to another entity or environment.
-
D.
waterExposure
Indicates that one entity is subjected to contact with water from another source or environment.
-
E.
exteriorMaterial
Indicates the material that forms the outer surface or outer construction of an object or structure.
- F. None of above. chosen
Provenance (4 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04eba51f08190ac5d9de7fc89405a |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda890140819082608931e993dd61 |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f3016c8190ac68d76e65e07af4 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:14 a.m.