Triple
T33436862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GeoPackage |
E856256
|
entity |
| Predicate | canStoreVectorFeatures |
P97573
|
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, canStoreVectorFeatures, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canStoreVectorFeatures Context triple: [GeoPackage, canStoreVectorFeatures, true]
-
A.
hasVector
Indicates that an entity is associated with, or can be represented by, a specific vector in some vector space.
-
B.
supportsVectorFormat
chosen
Indicates that one entity is capable of handling, processing, or outputting data in a vector-based format for another entity or context.
-
C.
isVectorValued
Indicates that a function or expression returns a vector (multiple components) rather than a single scalar value.
-
D.
usesScoringVector
Indicates that one entity evaluates or ranks another entity by applying a specific scoring vector or weighted set of criteria.
-
E.
canBeStoredFor
Indicates that something is suitable or allowed to be kept in storage for a certain duration or under certain conditions.
- 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_69f6e48699808190895ab15eeb97afa6 |
completed | May 3, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:36 a.m.