Triple
T37157763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Afghan buzkashi |
E920556
|
entity |
| Predicate | typicalPlayingField |
P119188
|
FINISHED |
| Object | large open field |
—
|
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: large open field | Statement: [Afghan buzkashi, typicalPlayingField, large open field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPlayingField Context triple: [Afghan buzkashi, typicalPlayingField, large open field]
-
A.
typicalGame
Indicates a relationship where one entity is characterized as a standard, representative, or commonly occurring example of a game for the other entity or context.
-
B.
fieldOfPlay
chosen
Indicates the spatial area or surface where an activity, event, or interaction takes place.
-
C.
typicalPlayingPosition
Indicates the usual role or position an entity regularly occupies when participating in a game, sport, or similar activity.
-
D.
typicalNumberOfPlayers
Indicates the usual or standard number of players involved in participating in an activity or game.
-
E.
fieldSide
Indicates the relative side or position of something with respect to a defined field or playing area.
- 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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.