Triple
T17282618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Standard for building stone (applicable classifications) |
E419567
|
entity |
| Predicate | appliesToUseCase |
P1129
|
FINISHED |
| Object | cladding 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: cladding stone | Statement: [British Standard for building stone (applicable classifications), appliesToUseCase, cladding stone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToUseCase Context triple: [British Standard for building stone (applicable classifications), appliesToUseCase, cladding stone]
-
A.
hasUseCase
Indicates that one entity is employed, applied, or utilized as a solution or method to address a particular need, problem, or scenario associated with another entity.
-
B.
appliesTo
chosen
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
C.
appliesToFeature
Indicates that something (such as a rule, constraint, or configuration) is relevant to, or governs, a specific feature.
-
D.
appliesVia
Indicates that an action, rule, or effect is carried out, implemented, or achieved through a specified method, medium, or mechanism.
-
E.
appliesFrom
Indicates that a rule, condition, or effect begins to be applicable starting from a specific point in time or state.
- 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e4332b19f481908acfa88b2f57c5dc |
completed | April 19, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69e3832c3b98819091967ac7e91ba316 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:40 a.m.