Triple
T31150158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nikon D6 |
E794049
|
entity |
| Predicate | hasBuiltInGPS |
P137837
|
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: [Nikon D6, hasBuiltInGPS, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuiltInGPS Context triple: [Nikon D6, hasBuiltInGPS, true]
-
A.
supportsA-GPS
Indicates that one entity provides compatibility with or functionality for Assisted GPS (A-GPS) for another entity.
-
B.
supportsGNSS
chosen
Indicates that one entity provides compatibility with or functional support for Global Navigation Satellite System (GNSS) capabilities for another entity.
-
C.
supportsGLONASS
Indicates that one entity provides compatibility with or operational support for the GLONASS satellite navigation system for another entity.
-
D.
hasSatelliteLocation
Indicates that an entity has a secondary or remote location associated with it, such as a branch, satellite office, or auxiliary site.
-
E.
hasNavigationTechnology
Indicates that an entity is equipped with or utilizes a system or technology for determining or guiding its position, route, or movement.
- 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_69f224d41bb48190a5621cd1485e3a30 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 29, 2026, 9:06 p.m.