Triple
T1935426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AirDrop |
E41432
|
entity |
| Predicate | transferMethod |
P27343
|
FINISHED |
| Object | direct device-to-device connection |
—
|
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: direct device-to-device connection | Statement: [AirDrop, transferMethod, direct device-to-device connection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transferMethod Context triple: [AirDrop, transferMethod, direct device-to-device connection]
-
A.
transferType
chosen
Indicates the specific method or category of how something is transferred from one entity to another.
-
B.
transferPolicy
Indicates a rule or set of conditions governing when and how something may be transferred from one party or location to another.
-
C.
hasTransfer
Indicates a relationship where something is moved or conveyed from one entity or location to another.
-
D.
topUpMethod
Indicates the method or mechanism used to add funds or value to an account, balance, or service.
-
E.
functionTransferredTo
Indicates that a specific function, role, or responsibility has been moved from one entity to another.
- 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_69a88649b24c819080047f26b6db2ded |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb29c7be08190986df157bf5d7c9e |
completed | March 7, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69abaff07cf88190b4883c5f17f90abd |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.