Triple
T33436856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GeoPackage |
E856256
|
entity |
| Predicate | isDesignedForMobileUse |
P9494
|
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, isDesignedForMobileUse, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDesignedForMobileUse Context triple: [GeoPackage, isDesignedForMobileUse, true]
-
A.
isDesignedFor
chosen
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
-
B.
isMobile
Indicates that an entity is capable of moving or being moved freely rather than remaining fixed in one place.
-
C.
designedForOneHandUse
Indicates that something is intended or optimized to be used comfortably and effectively with only one hand.
-
D.
isMobileBase
Indicates that an entity serves as a movable or mobile base or platform for other entities or operations.
-
E.
isDesignedAs
Indicates that something has been intentionally created or configured to serve as or function in the role of something else.
- 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.