Triple
T30726751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UWB |
E782296
|
entity |
| Predicate | hasAdvantageOverRFID |
P635
|
FINISHED |
| Object | two-way ranging capability |
—
|
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: two-way ranging capability | Statement: [UWB, hasAdvantageOverRFID, two-way ranging capability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdvantageOverRFID Context triple: [UWB, hasAdvantageOverRFID, two-way ranging capability]
-
A.
hasAdvantageOverBluetoothLowEnergy
Indicates that one technology, method, or system possesses benefits or superior characteristics compared to Bluetooth Low Energy.
-
B.
hasNFC
Indicates that one entity possesses or supports Near Field Communication (NFC) capability in relation to another entity or context.
-
C.
hasAdvantage
chosen
Indicates that one entity possesses a benefit, edge, or favorable position over another in a given context.
-
D.
isNFCChampion
Indicates that an entity has won the championship title of the National Football Conference (NFC) in a given season.
-
E.
advantageOverHAM-6
Indicates that one entity has a comparative advantage or superiority over another entity in the context of HAM-6.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: April 29, 2026, 8:37 p.m.