Triple
T10303049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Find My |
E241679
|
entity |
| Predicate | dataTransport |
P5991
|
FINISHED |
| Object | Bluetooth crowdsourced network |
—
|
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: Bluetooth crowdsourced network | Statement: [Find My, dataTransport, Bluetooth crowdsourced network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataTransport Context triple: [Find My, dataTransport, Bluetooth crowdsourced network]
-
A.
dataTransferType
chosen
Indicates the method or mode by which data is transmitted or exchanged between entities.
-
B.
materialTransportedTo
Indicates that a material is moved or conveyed from one location or entity to another specified destination.
-
C.
materialTransportedFrom
Indicates that a material or substance is moved or carried from a specified source location to another place.
-
D.
transportInterface
Indicates a relationship where one entity serves as the medium or mechanism through which another entity is transported or conveyed.
-
E.
transportAgnostic
Indicates that the relationship or action is independent of, and unaffected by, the specific transport mechanism or communication channel used.
- 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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d30846108190875042ab1c0204e0 |
completed | April 7, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f35e548190be3b4d92d65d2d20 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:45 a.m.