Triple
T33436866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GeoPackage |
E856256
|
entity |
| Predicate | usesSQLForDataAccess |
P5996
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [GeoPackage, usesSQLForDataAccess, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSQLForDataAccess Context triple: [GeoPackage, usesSQLForDataAccess, true]
-
A.
usesDatabases
Indicates that an entity employs one or more databases as part of its operations, functionality, or processes.
-
B.
usesAccessMethod
chosen
Indicates that one entity employs or relies on a particular access method to reach, interact with, or retrieve another entity or resource.
-
C.
usesDialect
Indicates that one entity communicates or expresses itself using the specific dialect associated with another entity.
-
D.
supportsDatabaseAbstraction
Indicates that one entity provides or enables a database abstraction layer for another, allowing interaction with databases independently of specific database implementations.
-
E.
supportsDatabaseConnectivity
Indicates that an entity provides the capability to establish and maintain connections to a database system.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: May 1, 2026, 1:36 a.m.