Triple
T18641646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Presidents Cup team |
E455702
|
entity |
| Predicate | inauguralEventCity |
P26157
|
FINISHED |
| Object | Prince William County, Virginia |
—
|
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: Prince William County, Virginia | Statement: [United States Presidents Cup team, inauguralEventCity, Prince William County, Virginia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inauguralEventCity Context triple: [United States Presidents Cup team, inauguralEventCity, Prince William County, Virginia]
-
A.
inauguralEvent
chosen
Indicates that an event is the first in a series or marks the formal beginning of a recurring activity, program, or institution.
-
B.
inauguralVenue
Indicates the location or facility where an event, organization, or activity was first officially launched or held.
-
C.
inaugurationLocation
Indicates the place where an inauguration event occurs or is held.
-
D.
inauguralEventDate
Indicates the calendar date on which an entity’s first or inaugural event took place.
-
E.
inaugurationEvent
Indicates an event in which a person is formally installed or inducted into an official position or office.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54fccafec8190a340356d5bbd3cdf |
completed | April 19, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69e478d85864819093cbad5ed9b54878 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:47 a.m.