Triple
T23135735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Amateur Four-Ball |
E577314
|
entity |
| Predicate | matchPlayStage |
P2703
|
FINISHED |
| Object | knockout bracket |
—
|
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: knockout bracket | Statement: [U.S. Amateur Four-Ball, matchPlayStage, knockout bracket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchPlayStage Context triple: [U.S. Amateur Four-Ball, matchPlayStage, knockout bracket]
-
A.
competitionStage
chosen
Indicates the specific phase or round within a broader competition in which the related entities participate or are situated.
-
B.
matchOf
Indicates that one entity is a specific match, counterpart, or corresponding instance of another entity within a defined context or set.
-
C.
matchBall
Indicates that an entity is associated with or participates in a particular ball used in a match or game.
-
D.
hasPhaseOfPlay
Indicates a relationship where a broader game or activity includes or is associated with a specific phase or segment of play.
-
E.
groupStageMatch
Indicates a match played between competitors during the group stage phase of a tournament or competition.
- 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_69e245f7b0e481909c473ff4e6a54e2c |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e8b694c8190b9ead00ea0576d90 |
completed | April 29, 2026, 4:52 a.m. |
| PD | Predicate disambiguation | batch_69ef89f83b108190aaaa1db6221fc163 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4 p.m.