Triple
T12309585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia E7 |
E293440
|
entity |
| Predicate | hasCompass |
P35891
|
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: [Nokia E7, hasCompass, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompass Context triple: [Nokia E7, hasCompass, yes]
-
A.
hasMagneticHeading
Indicates the directional orientation of an entity relative to magnetic north, typically expressed as a magnetic compass bearing.
-
B.
hasQiblaDirection
Indicates the directional relationship specifying which way one should face (toward the Kaaba in Mecca) for prayer.
-
C.
hasMagneticHeadingRangeInDegrees
Indicates the range of possible magnetic heading values, measured in degrees, associated with an entity’s orientation or navigation.
-
D.
hasNavigationTechnology
chosen
Indicates that an entity is equipped with or utilizes a system or technology for determining or guiding its position, route, or movement.
-
E.
hasNave
Indicates that one entity (typically a building or structure) possesses or includes a nave as a distinct architectural part.
- 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec02c008190a56aae60a3d9eff6 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.