Triple
T30270582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cavalry and Guards Club |
E769781
|
entity |
| Predicate | hasBarPolicy |
P181757
|
FINISHED |
| Object | members and guests only |
—
|
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: members and guests only | Statement: [Cavalry and Guards Club, hasBarPolicy, members and guests only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBarPolicy Context triple: [Cavalry and Guards Club, hasBarPolicy, members and guests only]
-
A.
hasBars
Indicates that one entity possesses, contains, or is equipped with bars as a defining feature or component.
-
B.
hasBarService
Indicates that one entity provides or features bar service for another entity or at a given location.
-
C.
hasBarStrength
Indicates that one entity possesses or exhibits a certain level or measure of bar-related strength or robustness in relation to another entity or context.
-
D.
hasBarLength
Indicates that an entity possesses a bar whose length is specified or measured.
-
E.
hasPolicySupport
Indicates that one entity provides endorsement, backing, or approval for a specific policy associated with another entity.
- 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_69f224856d9881908c7f0dd64f059672 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7824dc3f0819092a5102895b4a478 |
completed | May 3, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f7817c79e081908e685c48165e086b |
completed | May 3, 2026, 5:10 p.m. |
Created at: April 29, 2026, 7:43 p.m.