Triple
T12244572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FedEx Cup Playoffs |
E291818
|
entity |
| Predicate | fieldSizeAtTourChampionship |
P7759
|
FINISHED |
| Object | 30 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: 30 players | Statement: [FedEx Cup Playoffs, fieldSizeAtTourChampionship, 30 players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldSizeAtTourChampionship Context triple: [FedEx Cup Playoffs, fieldSizeAtTourChampionship, 30 players]
-
A.
fieldSize
chosen
Indicates the magnitude or dimensions of a field associated with an entity or context.
-
B.
playoffFieldSizeHistory
Indicates the historical sizes of the playoff field, showing how many participants qualified for the playoffs in different seasons or time periods.
-
C.
finalTournamentSlotsVariesByEdition
Indicates that the number or allocation of final tournament slots changes depending on the specific edition of the competition.
-
D.
numberOfTournaments
Indicates the total count of tournaments associated with or participated in by an entity.
-
E.
teamSizeAtPole
Indicates the number of team members present at a specific pole or pole location in the context of an activity or event.
- 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91d38ee10819093ed41d2954bf4ef |
completed | April 10, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69d91c46dcd88190a263db30804bff36 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.