Triple
T28531587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Francisco Pride |
E722055
|
entity |
| Predicate | hasGrandMarshals |
P145682
|
FINISHED |
| Object | community grand marshals |
—
|
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: community grand marshals | Statement: [San Francisco Pride, hasGrandMarshals, community grand marshals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGrandMarshals Context triple: [San Francisco Pride, hasGrandMarshals, community grand marshals]
-
A.
hasHonorees
chosen
Indicates that one entity is recognized or celebrated by listing another entity or entities as its honorees.
-
B.
ceremonyAttendedBy
Indicates that a particular ceremony was attended or participated in by a specified person or group.
-
C.
hasNotableHonoree
Indicates that an entity is notably dedicated to, named after, or honors a particular person or group.
-
D.
hasCoChairFrom
Indicates that an entity has a co-chair whose affiliation or origin is from a specified source, organization, or group.
-
E.
honoreeEligibility
Indicates that an entity meets the required conditions or qualifications to be selected or recognized as an honoree.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 28, 2026, 3:29 a.m.