Triple
T33967063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Francisco Yacht Club |
E870881
|
entity |
| Predicate | hasClubBurgee |
P193792
|
FINISHED |
| Object | burgee of the San Francisco Yacht Club |
—
|
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: burgee of the San Francisco Yacht Club | Statement: [San Francisco Yacht Club, hasClubBurgee, burgee of the San Francisco Yacht Club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClubBurgee Context triple: [San Francisco Yacht Club, hasClubBurgee, burgee of the San Francisco Yacht Club]
-
A.
hasClub
Indicates that an entity is associated with or belongs to a particular club.
-
B.
hasClubBase
Indicates that a club or organization is based at, or primarily operates from, a particular location or facility.
-
C.
hasHomeClub
Indicates that an entity (typically a person, such as an athlete) is associated with a particular club as their primary or official home organization.
-
D.
hasClubName
Indicates that an entity is associated with or identified by a specific club name.
-
E.
isStandOfClub
Indicates that a particular stand or section belongs to, is part of, or is designated for a specific club.
- 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_69f3499ce8e88190b66e1d49ad8c7037 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
| PDg | Predicate description generation | batch_69fd553c01488190b9fda48b4a728f04 |
completed | May 8, 2026, 3:15 a.m. |
Created at: May 1, 2026, 1:50 a.m.