Triple
T27086958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greco-Roman |
E686059
|
entity |
| Predicate | ruleSetDefinedBy |
P8188
|
FINISHED |
| Object | United World Wrestling rulebook |
—
|
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: United World Wrestling rulebook | Statement: [Greco-Roman, ruleSetDefinedBy, United World Wrestling rulebook]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruleSetDefinedBy Context triple: [Greco-Roman, ruleSetDefinedBy, United World Wrestling rulebook]
-
A.
proposedRuleSet
Indicates that one entity has put forward a specific set of rules or guidelines for consideration, adoption, or discussion by another entity or group.
-
B.
rulesBy
Indicates that one entity governs, controls, or exercises authoritative power over another entity.
-
C.
scopeDefinedBy
Indicates that the extent or boundaries of one entity’s applicability, influence, or validity are determined or constrained by another entity.
-
D.
baseDefinedBy
Indicates that something’s foundational properties, structure, or interpretation are determined or specified by a particular base or underlying system.
-
E.
setsRulesFor
chosen
Indicates that one entity establishes or defines rules, guidelines, or constraints that another entity is expected to follow.
- 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_69ef148940ec819097b5c20fbfbf7c81 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6234735cc819097c3f109e724b0a4 |
completed | May 2, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 8:38 a.m.