Triple
T10933916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shandur Polo Festival |
E258277
|
entity |
| Predicate | rulesCharacteristic |
P96708
|
FINISHED |
| Object | no formal polo rules |
—
|
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: no formal polo rules | Statement: [Shandur Polo Festival, rulesCharacteristic, no formal polo rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rulesCharacteristic Context triple: [Shandur Polo Festival, rulesCharacteristic, no formal polo rules]
-
A.
catalogCharacteristic
Indicates that a catalog has a specific characteristic or attribute associated with it.
-
B.
regulationCharacteristic
Indicates that one entity specifies, defines, or constrains a particular characteristic or property of another through a rule, standard, or regulatory condition.
-
C.
ruleCharacterization
Indicates that one rule is described, defined, or characterized in terms of another rule or set of rules.
-
D.
managementCharacteristic
Indicates a defining quality, style, or attribute associated with how something is managed or administered.
-
E.
policyCharacteristic
Indicates that a policy possesses a particular attribute, feature, or quality that characterizes how it is defined or operates.
- 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_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. |
| PDg | Predicate description generation | batch_69d7322370648190ba14cdd6fb4cdcb0 |
completed | April 9, 2026, 4:59 a.m. |
Created at: April 8, 2026, 9:23 p.m.