Triple
T32170645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Walk hut |
E821700
|
entity |
| Predicate | typicallyDoesNotProvide |
P101700
|
FINISHED |
| Object | bedding |
—
|
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: bedding | Statement: [Great Walk hut, typicallyDoesNotProvide, bedding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyDoesNotProvide Context triple: [Great Walk hut, typicallyDoesNotProvide, bedding]
-
A.
doesNotProvideFor
Indicates that one entity fails or is not responsible for supplying support, resources, or necessary provisions to another entity.
-
B.
doesNotServe
Indicates that one entity explicitly does not provide a service, function, or role to another entity.
-
C.
doesNotPrimarilyProvide
chosen
Indicates that one entity does not mainly or chiefly supply, offer, or furnish a particular service, resource, or function to another entity.
-
D.
doesNotAutomaticallyProvide
Indicates that something is not supplied or made available by default and requires an explicit action or request to be provided.
-
E.
mayNotProvide
Indicates that one entity is not permitted or is restricted from supplying, giving, or making another entity or resource available to another.
- 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_69f3490699a48190bbef96b198e8fade |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:33 a.m.