Triple
T8253623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twin Peaks Tavern |
E193015
|
entity |
| Predicate | windowPolicy |
P81211
|
FINISHED |
| Object | uncovered windows |
—
|
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: uncovered windows | Statement: [Twin Peaks Tavern, windowPolicy, uncovered windows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: windowPolicy Context triple: [Twin Peaks Tavern, windowPolicy, uncovered windows]
-
A.
locationPolicy
Indicates a rule or constraint governing where an entity is allowed, required, or restricted to be located.
-
B.
boardingPolicy
Indicates the rules or procedures governing how and in what order passengers are allowed to board a vehicle or vessel.
-
C.
issuesPolicyOn
Indicates that an authority or organization formally creates, approves, or enacts a policy concerning a particular subject or domain.
-
D.
transportPolicy
Indicates a relationship where an authority or organization defines rules, strategies, or guidelines governing how transportation systems are planned, operated, or regulated.
-
E.
walkInPolicy
Indicates that an entity allows or operates under a policy where individuals can arrive and be served without a prior appointment.
- 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_69ca82dfad9c8190b8cd18fb89f50f40 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb78cbc7cc81909931440e95d6e691 |
completed | March 31, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69cb36b6d5548190b665a6cce14c69f7 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb44d1caa881909069fa925a91316b |
completed | March 31, 2026, 3:51 a.m. |
Created at: March 30, 2026, 5:48 p.m.