Triple
T34269952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Correspondence Chess Championship |
E879283
|
entity |
| Predicate | usesDatabases |
P179107
|
FINISHED |
| Object | allowed |
—
|
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: allowed | Statement: [World Correspondence Chess Championship, usesDatabases, allowed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDatabases Context triple: [World Correspondence Chess Championship, usesDatabases, allowed]
-
A.
usedInDatabases
Indicates that something is employed or implemented within one or more database systems or database contexts.
-
B.
hasDatabase
Indicates that an entity possesses, uses, or is associated with a specific database.
-
C.
configuredPerDatabase
Indicates that something is set up or defined separately for each individual database.
-
D.
supportsDatabaseConnectivity
Indicates that an entity provides the capability to establish and maintain connections to a database system.
-
E.
hasOnlineDatabases
Indicates that an entity maintains or provides access to one or more databases that are available online.
- 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_69f349b4f5fc819094b441d18e95e5f1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f71c33edac8190a59f6ff19b265fc5 |
completed | May 3, 2026, 9:58 a.m. |
Created at: May 1, 2026, 1:56 a.m.