Triple
T27510315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Amateur Public Links Championship |
E694389
|
entity |
| Predicate | cutToMatchPlayFieldSize |
P156310
|
FINISHED |
| Object | 64 players |
—
|
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: 64 players | Statement: [U.S. Amateur Public Links Championship, cutToMatchPlayFieldSize, 64 players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cutToMatchPlayFieldSize Context triple: [U.S. Amateur Public Links Championship, cutToMatchPlayFieldSize, 64 players]
-
A.
matchPlayFieldSize
Indicates that two or more entities have playing fields or areas that are the same or compatible in size.
-
B.
fieldSizeAfterCut
chosen
Indicates the size or area of a field resulting after it has been cut or reduced from its original dimensions.
-
C.
hasShortGameArea
Indicates that an entity includes or is associated with a designated short-game practice area (e.g., for chipping, pitching, or putting).
-
D.
homeSoccerField
Indicates that a particular soccer field serves as the designated home field for a given team or organization.
-
E.
foalCrop
Indicates a relationship where a foal is associated with or produced from a particular crop or breeding outcome.
- 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_69ef53842afc8190ba6bd4e4999bda67 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62ef858008190bda723fb47853dce |
completed | May 2, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 1:15 p.m.