Triple
T10933874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shandur Polo Ground |
E258276
|
entity |
| Predicate | festivalIncludes |
P59845
|
FINISHED |
| Object | freestyle polo matches |
—
|
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: freestyle polo matches | Statement: [Shandur Polo Ground, festivalIncludes, freestyle polo matches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: festivalIncludes Context triple: [Shandur Polo Ground, festivalIncludes, freestyle polo matches]
-
A.
fiestaIncludes
chosen
Indicates that a particular fiesta or celebration event contains or features a specified element, such as an activity, performance, item, or participant.
-
B.
festivalAttracts
Indicates that a festival draws or brings in attendees, participants, or interest toward itself.
-
C.
festivalActivity
Indicates that an entity is an event, performance, or engagement that takes place as part of a festival’s organized program.
-
D.
determinesFestival
Indicates that one entity decides, defines, or selects which festival is applicable or will occur for another entity or context.
-
E.
exampleFestival
Indicates that an entity is an instance or example of a particular festival event or type of festival.
- 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_69d6aa8769b4819082bfe5e61b9017f0 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770ae073881909720febe9f5f296a |
completed | April 9, 2026, 9:26 a.m. |
| PD | Predicate disambiguation | batch_69d72e816a98819096d6c10dfb88a66a |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:23 p.m.