Triple
T27750353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Backgammon |
E702097
|
entity |
| Predicate | isGoverningBody |
P141916
|
FINISHED |
| Object | World Backgammon Federation |
—
|
NE NERFINISHED |
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: World Backgammon Federation | Statement: [Backgammon, isGoverningBody, World Backgammon Federation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGoverningBody Context triple: [Backgammon, isGoverningBody, World Backgammon Federation]
-
A.
governingBodyIncludes
Indicates that a governing body has a particular entity as one of its members or constituent parts.
-
B.
governingBodyOfType
Indicates that an entity serves as the official governing body for another entity of a specified type or category.
-
C.
organizationTypeOfGoverningBody
Indicates the type or classification of the organization that serves as the governing body for an entity.
-
D.
governingBodyRepresents
Indicates that a governing body acts on behalf of, and makes decisions representing the interests or authority of, another entity.
-
E.
governingBodyId
chosen
Indicates the entity that serves as the official governing body responsible for overseeing or managing another entity.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6371e33808190bd66d358dbd8d725 |
completed | May 2, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:19 p.m.