Triple
T33436846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GeoPackage |
E856256
|
entity |
| Predicate | supportsSpatialIndex |
P206471
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [GeoPackage, supportsSpatialIndex, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSpatialIndex Context triple: [GeoPackage, supportsSpatialIndex, yes]
-
A.
supportsSpatialQueries
Indicates that the subject system or component is capable of performing spatial (location- or geometry-based) queries on data.
-
B.
supportsSRID
Indicates that one entity provides compatibility with, recognition of, or operational support for a specified Spatial Reference System Identifier (SRID) associated with another entity.
-
C.
spatialFunction
Indicates a spatially defined role or function that one entity serves relative to another within a physical or geometric context.
-
D.
hasSpatialConcept
Indicates a relationship where one entity is associated with, defined by, or characterized through a particular spatial concept or spatial configuration.
-
E.
definesSpatialPredicate
Indicates that one entity specifies or establishes the spatial relationship or spatial condition that applies to another entity.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:36 a.m.