Triple
T9368523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Amateur Championship |
E225469
|
entity |
| Predicate | matchPlayFieldSize |
P88175
|
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: [The Amateur Championship, matchPlayFieldSize, 64 players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchPlayFieldSize Context triple: [The Amateur Championship, matchPlayFieldSize, 64 players]
-
A.
fieldSize
Indicates the magnitude or dimensions of a field associated with an entity or context.
-
B.
usesNumberOfPlayersOnFieldPerTeam
Indicates that the relationship specifies or depends on how many players each team has on the field at a given time.
-
C.
playoffFieldSizeHistory
Indicates the historical sizes of the playoff field, showing how many participants qualified for the playoffs in different seasons or time periods.
-
D.
homeSoccerField
Indicates that a particular soccer field serves as the designated home field for a given team or organization.
-
E.
playersPerSideOnField
Indicates the number of players from each team that are simultaneously present on the field during play.
- F. None of above. chosen
Provenance (4 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_69ca842cbddc819099d71ecec48cf9e5 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd5080f55c8190bd5ca0dc0a4ea989 |
completed | April 1, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69cc7a6abb8c81908c7a2f4ee92cc949 |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc955a38108190b602d1e73725f11b |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:43 p.m.