Triple
T22909862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Amateur |
E568559
|
entity |
| Predicate | firstEditionOrganizer |
P21090
|
FINISHED |
| Object | USGA |
—
|
NE NERFINISHED |
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: USGA | Statement: [U.S. Amateur, firstEditionOrganizer, USGA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstEditionOrganizer Context triple: [U.S. Amateur, firstEditionOrganizer, USGA]
-
A.
firstOrganizer
chosen
Indicates that an entity serves as the primary or initial organizer in relation to another event, group, or activity.
-
B.
firstEditionEvent
Indicates the event at which the first edition or initial release of a work was formally issued or made available.
-
C.
principalOrganizer
Indicates that an entity serves as the main or leading organizer responsible for planning or coordinating another entity or event.
-
D.
organizers
Indicates that one or more entities are responsible for planning, coordinating, or managing an event, activity, or group.
-
E.
co-organizerOf
Indicates that an entity shares responsibility with others in planning, coordinating, or managing an event, project, or activity.
- 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_69e2458cd9e48190943ad2e34485d939 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1807350008190a057e8fb5c363c5f |
completed | April 29, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69ef3b6b2e2481908258156937b5a745 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:42 p.m.