Triple
T9404964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IMU |
E226561
|
entity |
| Predicate | dataUsedWith |
P4791
|
FINISHED |
| Object | GPS receiver |
—
|
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: GPS receiver | Statement: [IMU, dataUsedWith, GPS receiver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataUsedWith Context triple: [IMU, dataUsedWith, GPS receiver]
-
A.
dataUse
Indicates how data is intended to be accessed, processed, or applied within a particular context or activity.
-
B.
usedWith
chosen
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
-
C.
technologyUsedBy
Indicates that a particular technology is employed or utilized by a specified entity.
-
D.
platformUsage
Indicates how an entity uses, engages with, or relies on a particular platform for its activities or services.
-
E.
usageAmong
Indicates how frequently or in what manner something is used within a particular group, context, or population.
- 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_69ca843170f88190800a8ab2b5fc568e |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd51c125dc8190a6438cf0ee23e7a9 |
completed | April 1, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69cca54c37f88190bddccf28e5fe5c84 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:46 p.m.